From 49dca95273a819f8a22353753e5f3fc79dc862e4 Mon Sep 17 00:00:00 2001 From: Avi Kivity Date: Thu, 25 Mar 2010 12:27:30 +0200 Subject: [PATCH] --- yaml --- r: 197710 b: refs/heads/master c: 8a5416db832895b84b85ad0bcbb11d1cce0d3d37 h: refs/heads/master v: v3 --- [refs] | 2 +- trunk/Documentation/kvm/api.txt | 18 ++++++++++++++++++ 2 files changed, 19 insertions(+), 1 deletion(-) diff --git a/[refs] b/[refs] index d46376dfe932..95752ce5c32d 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 0f2d8f4dd0663defff8c1738d33478c1fb65a4f5 +refs/heads/master: 8a5416db832895b84b85ad0bcbb11d1cce0d3d37 diff --git a/trunk/Documentation/kvm/api.txt b/trunk/Documentation/kvm/api.txt index 9d6e64753d29..2cc0120ccdb5 100644 --- a/trunk/Documentation/kvm/api.txt +++ b/trunk/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