linux-stable.git/include/linux/kvm.h, branch linux-2.6.29.y

KVM: Fix overlapping check for memory slots

2009-05-08T22:44:59+00:00

upstream commit: 4cd481f68dde99ac416003b825c835f71e364393

When checking for overlapping slots on registration of a new one, kvm
currently also considers zero-length (ie. deleted) slots and rejects
requests incorrectly. This finally denies user space from joining slots.
Fix the check by skipping deleted slots and advertise this via a
KVM_CAP_JOIN_MEMORY_REGIONS_WORKS.

Cc: stable@kernel.org
Signed-off-by: Jan Kiszka 
Signed-off-by: Avi Kivity 
Signed-off-by: Chris Wright

KVM: Avoid using CONFIG_ in userspace visible headers

2009-02-15T00:47:35+00:00

Kconfig symbols are not available in userspace, and are not stripped by
headers-install.  Avoid their use by adding #defines in  to
suit each architecture.

Signed-off-by: Avi Kivity

include of is preferred over

2009-01-16T00:39:41+00:00

Impact: fix 15 make headers_check warnings:

include of  is preferred over 

Signed-off-by: Jaswinder Singh Rajput 
Cc: Ingo Molnar 
Cc: Sam Ravnborg 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

KVM: x86: Rework user space NMI injection as KVM_CAP_USER_NMI

2008-12-31T14:55:47+00:00

There is no point in doing the ready_for_nmi_injection/
request_nmi_window dance with user space. First, we don't do this for
in-kernel irqchip anyway, while the code path is the same as for user
space irqchip mode. And second, there is nothing to loose if a pending
NMI is overwritten by another one (in contrast to IRQs where we have to
save the number). Actually, there is even the risk of raising spurious
NMIs this way because the reason for the held-back NMI might already be
handled while processing the first one.

Therefore this patch creates a simplified user space NMI injection
interface, exporting it under KVM_CAP_USER_NMI and dropping the old
KVM_CAP_NMI capability. And this time we also take care to provide the
interface only on archs supporting NMIs via KVM (right now only x86).

Signed-off-by: Jan Kiszka 
Signed-off-by: Avi Kivity

KVM: Advertise the bug in memory region destruction as fixed

2008-12-31T14:55:46+00:00

Userspace might need to act differently.

Signed-off-by: Avi Kivity

KVM: Enable MSI for device assignment

2008-12-31T14:55:02+00:00

We enable guest MSI and host MSI support in this patch. The userspace want to
enable MSI should set KVM_DEV_IRQ_ASSIGN_ENABLE_MSI in the assigned_irq's flag.
Function would return -ENOTTY if can't enable MSI, userspace shouldn't set MSI
Enable bit when KVM_ASSIGN_IRQ return -ENOTTY with
KVM_DEV_IRQ_ASSIGN_ENABLE_MSI.

Userspace can tell the support of MSI device from #ifdef KVM_CAP_DEVICE_MSI.

Signed-off-by: Sheng Yang 
Signed-off-by: Avi Kivity

KVM: Add fields for MSI device assignment

2008-12-31T14:55:01+00:00

Prepared for kvm_arch_assigned_device_msi_dispatch().

Signed-off-by: Sheng Yang 
Signed-off-by: Avi Kivity

KVM: x86: Support for user space injected NMIs

2008-12-31T14:51:42+00:00

Introduces the KVM_NMI IOCTL to the generic x86 part of KVM for
injecting NMIs from user space and also extends the statistic report
accordingly.

Based on the original patch by Sheng Yang.

Signed-off-by: Jan Kiszka 
Signed-off-by: Sheng Yang 
Signed-off-by: Avi Kivity

KVM: Future-proof device assignment ABI

2008-10-28T12:22:15+00:00

Reserve some space so we can add more data.

Signed-off-by: Avi Kivity

KVM: ia64: Add intel iommu support for guests.

2008-10-15T12:25:39+00:00

With intel iommu hardware, we can assign devices to kvm/ia64 guests.

Signed-off-by: Xiantao Zhang 
Signed-off-by: Avi Kivity