From: zhangyanfei <zhangyanfei@cn.fujitsu.com>
To: Avi Kivity <avi@redhat.com>, mtosatti@redhat.com
Cc: ebiederm@xmission.com, luto@mit.edu,
Joerg Roedel <joerg.roedel@amd.com>,
dzickus@redhat.com, paul.gortmaker@windriver.com,
ludwig.nussel@suse.de, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, kexec@lists.infradead.org,
Greg KH <gregkh@linuxfoundation.org>
Subject: [PATCH v2 5/5] Documentation: Add ABI entry for sysfs file vmcsinfo and vmcsinfo_maxsize
Date: Wed, 16 May 2012 15:57:35 +0800 [thread overview]
Message-ID: <4FB35DEF.2040008@cn.fujitsu.com> (raw)
In-Reply-To: <4FB35C48.30708@cn.fujitsu.com>
We create two new sysfs files, vmcsinfo and vmcsinfo_maxsize. And
here we add an Documentation/ABI entry for them.
Signed-off-by: zhangyanfei <zhangyanfei@cn.fujitsu.com>
---
Documentation/ABI/testing/sysfs-kernel-vmcsinfo | 16 ++++++++++++++++
1 files changed, 16 insertions(+), 0 deletions(-)
create mode 100644 Documentation/ABI/testing/sysfs-kernel-vmcsinfo
diff --git a/Documentation/ABI/testing/sysfs-kernel-vmcsinfo b/Documentation/ABI/testing/sysfs-kernel-vmcsinfo
new file mode 100644
index 0000000..adbf866
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-kernel-vmcsinfo
@@ -0,0 +1,16 @@
+What: /sys/kernel/vmcsinfo
+Date: April 2012
+KernelVersion: 3.4.0
+Contact: Zhang Yanfei <zhangyanfei@cn.fujitsu.com>
+Description
+ Shows physical address of VMCSINFO. VMCSINFO contains
+ the VMCS revision identifier and encoded offsets of fields
+ in VMCS data on Intel processors equipped with the VT
+ extensions.
+
+What: /sys/kernel/vmcsinfo_maxsize
+Date: April 2012
+KernelVersion: 3.4.0
+Contact: Zhang Yanfei <zhangyanfei@cn.fujitsu.com>
+Description
+ Shows max size of VMCSINFO.
--
1.7.1
next prev parent reply other threads:[~2012-05-16 7:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 7:50 [PATCH v2 0/5] Export offsets of VMCS fields as note information for kdump zhangyanfei
2012-05-16 7:52 ` [PATCH v2 1/5] x86: Add helper variables and functions to hold VMCSINFO zhangyanfei
2012-06-14 13:28 ` Avi Kivity
2012-05-16 7:54 ` [PATCH v2 2/5] KVM: Export symbols for module vmcsinfo-intel zhangyanfei
2012-05-16 7:55 ` [PATCH v2 3/5] KVM-INTEL: Add new module vmcsinfo-intel to fill VMCSINFO zhangyanfei
2012-06-14 13:37 ` Avi Kivity
2012-06-15 3:03 ` HATAYAMA Daisuke
2012-05-16 7:56 ` [PATCH v2 4/5] ksysfs: Export VMCSINFO via sysfs zhangyanfei
2012-05-16 7:57 ` zhangyanfei [this message]
2012-06-14 13:21 ` [PATCH v2 5/5] Documentation: Add ABI entry for sysfs file vmcsinfo and vmcsinfo_maxsize Avi Kivity
2012-05-20 17:43 ` [PATCH v2 0/5] Export offsets of VMCS fields as note information for kdump Avi Kivity
2012-05-21 2:32 ` Yanfei Zhang
2012-05-21 8:34 ` Avi Kivity
2012-05-21 9:08 ` Yanfei Zhang
2012-05-21 9:36 ` Avi Kivity
2012-05-22 3:40 ` Yanfei Zhang
2012-05-28 5:25 ` Yanfei Zhang
2012-05-28 13:28 ` Avi Kivity
2012-05-29 7:06 ` Yanfei Zhang
2012-06-11 5:35 ` Yanfei Zhang
2012-06-14 13:15 ` Avi Kivity
2012-06-18 7:25 ` YOSHIDA Masanori
2012-05-21 18:58 ` Eric Northup
2012-05-22 3:53 ` Yanfei Zhang
2012-05-22 20:53 ` Eric Northup
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FB35DEF.2040008@cn.fujitsu.com \
--to=zhangyanfei@cn.fujitsu.com \
--cc=avi@redhat.com \
--cc=dzickus@redhat.com \
--cc=ebiederm@xmission.com \
--cc=gregkh@linuxfoundation.org \
--cc=joerg.roedel@amd.com \
--cc=kexec@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludwig.nussel@suse.de \
--cc=luto@mit.edu \
--cc=mtosatti@redhat.com \
--cc=paul.gortmaker@windriver.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox