KVM: trivial document fixes

   Only run vcpu ioctls from the same thread that was used to create the

   vcpu.

2. File descritpors

2. File descriptors

The kvm API is centered around file descriptors.  An initial

open("/dev/kvm") obtains a handle to the kvm subsystem; this handle

can be used to issue system ioctls.  A KVM_CREATE_VM ioctl on this

handle will create a VM file descripror which can be used to issue VM

handle will create a VM file descriptor which can be used to issue VM

ioctls.  A KVM_CREATE_VCPU ioctl on a VM fd will create a virtual cpu

and return a file descriptor pointing to it.  Finally, ioctls on a vcpu

fd can be used to control the vcpu, including the important task of

Parameters: struct kvm_clock_data (in)

Returns: 0 on success, -1 on error

Sets the current timestamp of kvmclock to the valued specific in its parameter.

Sets the current timestamp of kvmclock to the value specified in its parameter.

In conjunction with KVM_GET_CLOCK, it is used to ensure monotonicity on scenarios

such as migration.

			__u64 data_offset; /* relative to kvm_run start */

		} io;

If exit_reason is KVM_EXIT_IO_IN or KVM_EXIT_IO_OUT, then the vcpu has

If exit_reason is KVM_EXIT_IO, then the vcpu has

executed a port I/O instruction which could not be satisfied by kvm.

data_offset describes where the data is located (KVM_EXIT_IO_OUT) or

where kvm expects application code to place the data for the next

KVM_RUN invocation (KVM_EXIT_IO_IN).  Data format is a patcked array.

KVM_RUN invocation (KVM_EXIT_IO_IN).  Data format is a packed array.

		struct {

			struct kvm_debug_exit_arch arch;

			__u8  is_write;

		} mmio;

If exit_reason is KVM_EXIT_MMIO or KVM_EXIT_IO_OUT, then the vcpu has

If exit_reason is KVM_EXIT_MMIO, then the vcpu has

executed a memory-mapped I/O instruction which could not be satisfied

by kvm.  The 'data' member contains the written data if 'is_write' is

true, and should be filled by application code otherwise.