From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Juergen Gross <jgross@suse.com>,
linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org
Cc: gregkh@linuxfoundation.org
Subject: Re: [PATCH v2 2/2] xen: add sysfs node for guest type
Date: Fri, 26 May 2017 10:18:48 -0400 [thread overview]
Message-ID: <14c0303e-35d3-6e72-e38b-501a26a2a3a9@oracle.com> (raw)
In-Reply-To: <20170526125657.24505-3-jgross@suse.com>
On 05/26/2017 08:56 AM, Juergen Gross wrote:
> Currently there is no reliable user interface inside a Xen guest to
> determine its type (e.g. HVM, PV or PVH). Instead of letting user mode
> try to determine this by various rather hacky mechanisms (parsing of
> boot messages before they are gone, trying to make use of known subtle
> differences in behavior of some instructions), add a sysfs node
> /sys/hypervisor/guest_type to explicitly deliver this information as
> it is known to the kernel.
>
> Signed-off-by: Juergen Gross <jgross@suse.com>
Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
(I would have preferred to have /sys/hypervisor/xen/ but given that some
of the other files have been around for ages, and are now declared
stable, it's too late).
prev parent reply other threads:[~2017-05-26 14:19 UTC|newest]
Thread overview: 5+ 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 ` [PATCH v2 1/2] doc,xen: document hypervisor sysfs nodes for xen Juergen Gross
2017-05-26 13:32 ` [Xen-devel] [PATCH v2 1/2] doc, xen: " Andrew Cooper
2017-05-26 12:56 ` [PATCH v2 2/2] xen: add sysfs node for guest type Juergen Gross
2017-05-26 14:18 ` Boris Ostrovsky [this message]
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=14c0303e-35d3-6e72-e38b-501a26a2a3a9@oracle.com \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®