From: Juergen Gross <jgross@suse.com>
To: linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org
Cc: boris.ostrovsky@oracle.com, gregkh@linuxfoundation.org,
Juergen Gross <jgross@suse.com>
Subject: [PATCH v4 0/4] xen: add xen sysfs nodes
Date: Wed, 14 Jun 2017 19:23:48 +0200 [thread overview]
Message-ID: <20170614172352.27557-1-jgross@suse.com> (raw)
In order to be able to determine the Xen guest type from within the
guest as a user there is currently no stable interface available.
Add a sysfs node for that purpose as the guest type information is
available for the kernel.
While doing this document all the other Xen related sysfs nodes.
Add another node to show the Xen hypervisor buildid in order to make
hypervisor live patching easier.
Juergen Gross (4):
doc,xen: document hypervisor sysfs nodes for xen
xen: add sysfs node for guest type
xen: sync include/xen/interface/version.h
xen: add sysfs node for hypervisor build id
Documentation/ABI/stable/sysfs-hypervisor-xen | 119 +++++++++++++++++++++
.../{sysfs-hypervisor-pmu => sysfs-hypervisor-xen} | 24 ++++-
MAINTAINERS | 2 +
drivers/xen/sys-hypervisor.c | 59 ++++++++++
include/xen/interface/version.h | 15 +++
5 files changed, 217 insertions(+), 2 deletions(-)
create mode 100644 Documentation/ABI/stable/sysfs-hypervisor-xen
rename Documentation/ABI/testing/{sysfs-hypervisor-pmu => sysfs-hypervisor-xen} (54%)
--
2.12.3
next reply other threads:[~2017-06-14 17:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 17:23 Juergen Gross [this message]
2017-06-14 17:23 ` [PATCH v4 1/4] doc,xen: document hypervisor sysfs nodes for xen Juergen Gross
2017-06-14 17:23 ` [PATCH v4 2/4] xen: add sysfs node for guest type Juergen Gross
2017-06-14 17:43 ` Boris Ostrovsky
2017-06-14 18:52 ` Juergen Gross
2017-06-14 18:56 ` Boris Ostrovsky
2017-06-14 17:23 ` [PATCH v4 3/4] xen: sync include/xen/interface/version.h Juergen Gross
2017-06-14 17:23 ` [PATCH v4 4/4] xen: add sysfs node for hypervisor build id Juergen Gross
2017-06-14 17:45 ` 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=20170614172352.27557-1-jgross@suse.com \
--to=jgross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=gregkh@linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).