From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Juergen Gross <jgross@suse.com>,
linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org
Cc: gregkh@linuxfoundation.org, boris.ostrovsky@oracle.com
Subject: Re: [PATCH v2 1/2] doc, xen: document hypervisor sysfs nodes for xen
Date: Fri, 26 May 2017 14:32:10 +0100 [thread overview]
Message-ID: <a2f2ba1b-e041-5715-6190-e4c72b20a948__34758.8159879253$1495805610$gmane$org@citrix.com> (raw)
In-Reply-To: <20170526125657.24505-2-jgross@suse.com>
On 26/05/17 13:56, Juergen Gross wrote:
> Today only a few sysfs nodes under /sys/hypervisor/ are documented
> for Xen in Documentation/ABI/testing/sysfs-hypervisor-pmu.
>
> Add the remaining Xen sysfs nodes under /sys/hypervisor/ in a new
> file Documentation/ABI/stable/sysfs-hypervisor-xen and add the Xen
> specific sysfs docs to the MAINTAINERS file.
>
> Signed-off-by: Juergen Gross <jgross@suse.com>
> ---
> V2:
> - rename file to Documentation/ABI/stable/sysfs-hypervisor-xen in
> order to reflect Xen dependency
> - leave pmu entries in old file under testing (Boris Ostrovsky)
> ---
> Documentation/ABI/stable/sysfs-hypervisor-xen | 107 ++++++++++++++++++++++++++
> MAINTAINERS | 2 +
> 2 files changed, 109 insertions(+)
> create mode 100644 Documentation/ABI/stable/sysfs-hypervisor-xen
>
> diff --git a/Documentation/ABI/stable/sysfs-hypervisor-xen b/Documentation/ABI/stable/sysfs-hypervisor-xen
> new file mode 100644
> index 000000000000..97e4171508c4
> --- /dev/null
> +++ b/Documentation/ABI/stable/sysfs-hypervisor-xen
> @@ -0,0 +1,107 @@
> +What: /sys/hypervisor/compilation/compile_date
> +Date: March 2009
> +KernelVersion: 2.6.30
> +Contact: xen-devel@lists.xenproject.org
> +Description: If running under Xen:
> + Contains the build time stamp of the Xen hypervisor
> +
> +What: /sys/hypervisor/compilation/compiled_by
> +Date: March 2009
> +KernelVersion: 2.6.30
> +Contact: xen-devel@lists.xenproject.org
> +Description: If running under Xen:
> + Contains information who built the Xen hypervisor
> +
> +What: /sys/hypervisor/compilation/compiler
> +Date: March 2009
> +KernelVersion: 2.6.30
> +Contact: xen-devel@lists.xenproject.org
> +Description: If running under Xen:
> + Compiler which was used to build the Xen hypervisor
> +
> +What: /sys/hypervisor/properties/capabilities
> +Date: March 2009
> +KernelVersion: 2.6.30
> +Contact: xen-devel@lists.xenproject.org
> +Description: If running under Xen:
> + Space separated list of supported guest system types. Each type
> + is in the format: <class>-<major>.<minor>-<arch>
> + With:
> + <class>: "xen" -- x86: paravirtualized, arm: standard
> + "hvm" -- x86 only: full virtualized
> + <major>: major guest interface version
> + <minor>: minor guest interface version
> + <arch>: architecture, e.g.:
> + "x86_32": 32 bit x86 guest without PAE
> + "x86_32p": 32 bit x86 guest with PAE
> + "x86_64": 64 bit x86 guest
> + "armv7l": 32 bit arm guest
> + "aarch64": 64 bit arm guest
> +
> +What: /sys/hypervisor/properties/changeset
> +Date: March 2009
> +KernelVersion: 2.6.30
> +Contact: xen-devel@lists.xenproject.org
> +Description: If running under Xen:
> + Changeset of the hypervisor (git commit)
> +
> +What: /sys/hypervisor/properties/features
> +Date: March 2009
> +KernelVersion: 2.6.30
> +Contact: xen-devel@lists.xenproject.org
> +Description: If running under Xen:
> + Features the Xen hypervisor supports for the guest as defined
> + in include/xen/interface/features.h printed as a hex value.
> +
> +What: /sys/hypervisor/properties/pagesize
> +Date: March 2009
> +KernelVersion: 2.6.30
> +Contact: xen-devel@lists.xenproject.org
> +Description: If running under Xen:
> + Default page size of the hypervisor printed as a hex value.
> +
> +What: /sys/hypervisor/properties/virtual_start
> +Date: March 2009
> +KernelVersion: 2.6.30
> +Contact: xen-devel@lists.xenproject.org
> +Description: If running under Xen:
> + Virtual address of the hypervisor as a hex value.
All properties above here, as well as "extra" below, may be deliberately
elided by Xen. Is it perhaps worth having a general note to this effect
at the top of the file?
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-05-26 13:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 12:56 [PATCH v2 0/2] xen: add xen sysfs node Juergen Gross
2017-05-26 12:56 ` Juergen Gross
2017-05-26 12:56 ` [PATCH v2 1/2] doc,xen: document hypervisor sysfs nodes for xen Juergen Gross
2017-05-26 12:56 ` [PATCH v2 1/2] doc, xen: " Juergen Gross
2017-05-26 13:32 ` Andrew Cooper [this message]
2017-05-26 13:32 ` [Xen-devel] " Andrew Cooper
2017-05-26 12:56 ` [PATCH v2 2/2] xen: add sysfs node for guest type Juergen Gross
2017-05-26 12:56 ` Juergen Gross
2017-05-26 14:18 ` Boris Ostrovsky
2017-05-26 14:18 ` Boris Ostrovsky
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='a2f2ba1b-e041-5715-6190-e4c72b20a948__34758.8159879253$1495805610$gmane$org@citrix.com' \
--to=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xenproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.