summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAvi Kivity <avi@redhat.com>2010-03-25 10:27:30 (GMT)
committerAvi Kivity <avi@redhat.com>2010-05-17 09:16:47 (GMT)
commit8a5416db832895b84b85ad0bcbb11d1cce0d3d37 (patch)
tree84d7f8e03d5d76cffe69caa5c08d32f242f51417
parent0f2d8f4dd0663defff8c1738d33478c1fb65a4f5 (diff)
downloadlinux-fsl-qoriq-8a5416db832895b84b85ad0bcbb11d1cce0d3d37.tar.xz
KVM: Document KVM_SET_TSS_ADDR
Signed-off-by: Avi Kivity <avi@redhat.com>
-rw-r--r--Documentation/kvm/api.txt18
1 files changed, 18 insertions, 0 deletions
diff --git a/Documentation/kvm/api.txt b/Documentation/kvm/api.txt
index 9d6e647..2cc0120 100644
--- a/Documentation/kvm/api.txt
+++ b/Documentation/kvm/api.txt
@@ -795,6 +795,24 @@ It is recommended to use this API instead of the KVM_SET_MEMORY_REGION ioctl.
The KVM_SET_MEMORY_REGION does not allow fine grained control over memory
allocation and is deprecated.
+4.35 KVM_SET_TSS_ADDR
+
+Capability: KVM_CAP_SET_TSS_ADDR
+Architectures: x86
+Type: vm ioctl
+Parameters: unsigned long tss_address (in)
+Returns: 0 on success, -1 on error
+
+This ioctl defines the physical address of a three-page region in the guest
+physical address space. The region must be within the first 4GB of the
+guest physical address space and must not conflict with any memory slot
+or any mmio address. The guest may malfunction if it accesses this memory
+region.
+
+This ioctl is required on Intel-based hosts. This is needed on Intel hardware
+because of a quirk in the virtualization implementation (see the internals
+documentation when it pops into existence).
+
5. The kvm_run structure
Application code obtains a pointer to the kvm_run structure by