|
|
@@ -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
|
Avi Kivity