From: Avi Kivity Subject: [PATCH 2/2] KVM: Document KVM_SET_TSS_ADDR Date: Thu, 25 Mar 2010 12:31:39 +0200 Message-ID: <1269513099-21060-3-git-send-email-avi@redhat.com> References: <1269513099-21060-1-git-send-email-avi@redhat.com> Cc: Pekka Enberg , Marcelo Tosatti To: kvm@vger.kernel.org Return-path: Received: from mx1.redhat.com ([209.132.183.28]:53822 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754043Ab0CYKbo (ORCPT ); Thu, 25 Mar 2010 06:31:44 -0400 In-Reply-To: <1269513099-21060-1-git-send-email-avi@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: Signed-off-by: Avi Kivity --- 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 +++ b/Documentation/kvm/api.txt @@ -793,6 +793,22 @@ is madvise(MADV_DROP). It is recommended to use this API instead of the KVM_SET_MEMORY_REGION ioctl. +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. + 5. The kvm_run structure Application code obtains a pointer to the kvm_run structure by -- 1.7.0.2