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

KVM: x86: Add KVM_CAP_X86_ROBUST_SINGLESTEP

2010-04-01T23:01:19+00:00

Commit d2be1651b736002e0c76d7095d6c0ba77b4a897c upstream.

This marks the guest single-step API improvement of 94fe45da and
91586a3b with a capability flag to allow reliable detection by user
space.

Signed-off-by: Jan Kiszka 
Signed-off-by: Greg Kroah-Hartman

Merge commit 'origin/master' into next

2009-12-09T06:14:38+00:00

Conflicts:
	include/linux/kvm.h

powerpc/kvm: Sync guest visible MMU state

2009-12-08T05:02:50+00:00

Currently userspace has no chance to find out which virtual address space we're
in and resolve addresses. While that is a big problem for migration, it's also
unpleasent when debugging, as gdb and the monitor don't work on virtual
addresses.

This patch exports enough of the MMU segment state to userspace to make
debugging work and thus also includes the groundwork for migration.

Signed-off-by: Alexander Graf 
Signed-off-by: Benjamin Herrenschmidt

KVM: s390: Make psw available on all exits, not just a subset

2009-12-03T07:32:25+00:00

This patch moves s390 processor status word into the base kvm_run
struct and keeps it up-to date on all userspace exits.

The userspace ABI is broken by this, however there are no applications
in the wild using this.  A capability check is provided so users can
verify the updated API exists.

Cc: stable@kernel.org
Signed-off-by: Carsten Otte 
Signed-off-by: Avi Kivity

KVM: x86: Add KVM_GET/SET_VCPU_EVENTS

2009-12-03T07:32:25+00:00

This new IOCTL exports all yet user-invisible states related to
exceptions, interrupts, and NMIs. Together with appropriate user space
changes, this fixes sporadic problems of vmsave/restore, live migration
and system reset.

[avi: future-proof abi by adding a flags field]

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

KVM: VMX: Report unexpected simultaneous exceptions as internal errors

2009-12-03T07:32:24+00:00

These happen when we trap an exception when another exception is being
delivered; we only expect these with MCEs and page faults.  If something
unexpected happens, things probably went south and we're better off reporting
an internal error and freezing.

Signed-off-by: Avi Kivity

KVM: Allow internal errors reported to userspace to carry extra data

2009-12-03T07:32:24+00:00

Usually userspace will freeze the guest so we can inspect it, but some
internal state is not available.  Add extra data to internal error
reporting so we can expose it to the debugger.  Extra data is specific
to the suberror.

Signed-off-by: Avi Kivity

KVM: Reorder IOCTLs in main kvm.h

2009-12-03T07:32:24+00:00

Obviously, people tend to extend this header at the bottom - more or
less blindly. Ensure that deprecated stuff gets its own corner again by
moving things to the top. Also add some comments and reindent IOCTLs to
make them more readable and reduce the risk of number collisions.

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

KVM: allow userspace to adjust kvmclock offset

2009-12-03T07:32:19+00:00

When we migrate a kvm guest that uses pvclock between two hosts, we may
suffer a large skew. This is because there can be significant differences
between the monotonic clock of the hosts involved. When a new host with
a much larger monotonic time starts running the guest, the view of time
will be significantly impacted.

Situation is much worse when we do the opposite, and migrate to a host with
a smaller monotonic clock.

This proposed ioctl will allow userspace to inform us what is the monotonic
clock value in the source host, so we can keep the time skew short, and
more importantly, never goes backwards. Userspace may also need to trigger
the current data, since from the first migration onwards, it won't be
reflected by a simple call to clock_gettime() anymore.

[marcelo: future-proof abi with a flags field]
[jan: fix KVM_GET_CLOCK by clearing flags field instead of checking it]

Signed-off-by: Glauber Costa 
Signed-off-by: Marcelo Tosatti 
Signed-off-by: Avi Kivity

KVM: Xen PV-on-HVM guest support

2009-12-03T07:32:18+00:00

Support for Xen PV-on-HVM guests can be implemented almost entirely in
userspace, except for handling one annoying MSR that maps a Xen
hypercall blob into guest address space.

A generic mechanism to delegate MSR writes to userspace seems overkill
and risks encouraging similar MSR abuse in the future.  Thus this patch
adds special support for the Xen HVM MSR.

I implemented a new ioctl, KVM_XEN_HVM_CONFIG, that lets userspace tell
KVM which MSR the guest will write to, as well as the starting address
and size of the hypercall blobs (one each for 32-bit and 64-bit) that
userspace has loaded from files.  When the guest writes to the MSR, KVM
copies one page of the blob from userspace to the guest.

I've tested this patch with a hacked-up version of Gerd's userspace
code, booting a number of guests (CentOS 5.3 i386 and x86_64, and
FreeBSD 8.0-RC1 amd64) and exercising PV network and block devices.

[jan: fix i386 build warning]
[avi: future proof abi with a flags field]

Signed-off-by: Ed Swierk 
Signed-off-by: Jan Kiszka 
Signed-off-by: Marcelo Tosatti 
Signed-off-by: Avi Kivity