linux-toradex.git/include/linux/kvm_host.h, branch v2.6.35.4

KVM: Let vcpu structure alignment be determined at runtime

2010-05-19T08:36:29+00:00

vmx and svm vcpus have different contents and therefore may have different
alignmment requirements.  Let each specify its required alignment.

Signed-off-by: Avi Kivity

KVM: Get rid of dead function gva_to_page()

2010-05-17T09:18:10+00:00

Nobody use gva_to_page() anymore, get rid of it.

Signed-off-by: Gui Jianfeng 
Signed-off-by: Avi Kivity

KVM: use the correct RCU API for PROVE_RCU=y

2010-05-17T09:18:01+00:00

The RCU/SRCU API have already changed for proving RCU usage.

I got the following dmesg when PROVE_RCU=y because we used incorrect API.
This patch coverts rcu_deference() to srcu_dereference() or family API.

===================================================
[ INFO: suspicious rcu_dereference_check() usage. ]
---------------------------------------------------
arch/x86/kvm/mmu.c:3020 invoked rcu_dereference_check() without protection!

other info that might help us debug this:

rcu_scheduler_active = 1, debug_locks = 0
2 locks held by qemu-system-x86/8550:
 #0:  (&kvm->slots_lock){+.+.+.}, at: [] kvm_set_memory_region+0x29/0x50 [kvm]
 #1:  (&(&kvm->mmu_lock)->rlock){+.+...}, at: [] kvm_arch_commit_memory_region+0xa6/0xe2 [kvm]

stack backtrace:
Pid: 8550, comm: qemu-system-x86 Not tainted 2.6.34-rc4-tip-01028-g939eab1 #27
Call Trace:
 [] lockdep_rcu_dereference+0xaa/0xb3
 [] kvm_mmu_calculate_mmu_pages+0x44/0x7d [kvm]
 [] kvm_arch_commit_memory_region+0xb7/0xe2 [kvm]
 [] __kvm_set_memory_region+0x636/0x6e2 [kvm]
 [] kvm_set_memory_region+0x37/0x50 [kvm]
 [] vmx_set_tss_addr+0x46/0x5a [kvm_intel]
 [] kvm_arch_vm_ioctl+0x17a/0xcf8 [kvm]
 [] ? unlock_page+0x27/0x2c
 [] ? __do_fault+0x3a9/0x3e1
 [] kvm_vm_ioctl+0x364/0x38d [kvm]
 [] ? up_read+0x23/0x3d
 [] vfs_ioctl+0x32/0xa6
 [] do_vfs_ioctl+0x495/0x4db
 [] ? fget_light+0xc2/0x241
 [] ? do_sys_open+0x104/0x116
 [] ? retint_swapgs+0xe/0x13
 [] sys_ioctl+0x47/0x6a
 [] system_call_fastpath+0x16/0x1b

Signed-off-by: Lai Jiangshan 
Signed-off-by: Avi Kivity

KVM: limit the number of pages per memory slot

2010-05-17T09:17:41+00:00

This patch limits the number of pages per memory slot to make
us free from extra care about type issues.

Signed-off-by: Takuya Yoshikawa 
Signed-off-by: Marcelo Tosatti

KVM: Increase NR_IOBUS_DEVS limit to 200

2010-04-20T10:08:30+00:00

This patch increases the current hardcoded limit of NR_IOBUS_DEVS
from 6 to 200. We are hitting this limit when creating a guest with more
than 1 virtio-net device using vhost-net backend. Each virtio-net
device requires 2 such devices to service notifications from rx/tx queues.

Signed-off-by: Sridhar Samudrala 
Signed-off-by: Avi Kivity

KVM: fix the handling of dirty bitmaps to avoid overflows

2010-04-20T10:06:55+00:00

Int is not long enough to store the size of a dirty bitmap.

This patch fixes this problem with the introduction of a wrapper
function to calculate the sizes of dirty bitmaps.

Note: in mark_page_dirty(), we have to consider the fact that
  __set_bit() takes the offset as int, not long.

Signed-off-by: Takuya Yoshikawa 
Signed-off-by: Marcelo Tosatti

KVM: Convert kvm->requests_lock to raw_spinlock_t

2010-03-01T15:36:13+00:00

The code relies on kvm->requests_lock inhibiting preemption.

Noted by Jan Kiszka.

Signed-off-by: Avi Kivity

KVM: Introduce kvm_host_page_size

2010-03-01T15:36:08+00:00

This patch introduces a generic function to find out the
host page size for a given gfn. This function is needed by
the kvm iommu code. This patch also simplifies the x86
host_mapping_level function.

Signed-off-by: Joerg Roedel 
Signed-off-by: Avi Kivity

KVM: enable PCI multiple-segments for pass-through device

2010-03-01T15:36:06+00:00

Enable optional parameter (default 0) - PCI segment (or domain) besides
BDF, when assigning PCI device to guest.

Signed-off-by: Zhai Edwin 
Acked-by: Chris Wright 
Signed-off-by: Marcelo Tosatti

KVM: Lazify fpu activation and deactivation

2010-03-01T15:35:50+00:00

Defer fpu deactivation as much as possible - if the guest fpu is loaded, keep
it loaded until the next heavyweight exit (where we are forced to unload it).
This reduces unnecessary exits.

We also defer fpu activation on clts; while clts signals the intent to use the
fpu, we can't be sure the guest will actually use it.

Signed-off-by: Avi Kivity