Signed-off-by: Avi Kivity a...@redhat.com
---
Documentation/kvm/api.txt | 16
1 files changed, 16 insertions(+), 0 deletions(-)
diff --git a/Documentation/kvm/api.txt b/Documentation/kvm/api.txt
index 22af28a..8f45099 100644
--- a/Documentation/kvm/api.txt
+++
Hi Avi,
Avi Kivity kirjoitti:
Signed-off-by: Avi Kivity a...@redhat.com
---
Documentation/kvm/api.txt | 16
1 files changed, 16 insertions(+), 0 deletions(-)
diff --git a/Documentation/kvm/api.txt b/Documentation/kvm/api.txt
index 22af28a..8f45099 100644
---
On 03/25/2010 12:36 PM, Pekka Enberg wrote:
+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
Avi Kivity kirjoitti:
On 03/25/2010 12:36 PM, Pekka Enberg wrote:
+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
On 03/25/2010 02:00 PM, Pekka Enberg wrote:
I don't think such a technical description of an implementation
detail has a place in the API reference; maybe in internal
documentation.
Sure but it would be nice to have something along the lines of This
is needed on Intel hardware because of a