From: Anthony Liguori <anthony@codemonkey.ws>
To: Glauber Costa <glommer@gmail.com>
Cc: Bryan McLellan <btm@loftninjas.org>, kvm@vger.kernel.org
Subject: Re: Accessing pv_info from userland
Date: Sat, 31 Jan 2009 15:08:55 -0600 [thread overview]
Message-ID: <4984BDE7.2060503@codemonkey.ws> (raw)
In-Reply-To: <5d6222a80901311155l2c20fa0aw8cabdac5e6f3caaa@mail.gmail.com>
Glauber Costa wrote:
> On Sat, Jan 31, 2009 at 5:36 PM, Anthony Liguori <anthony@codemonkey.ws> wrote:
>
>> Since this is a pretty standard mechanism, it may make sense to include this
>> signature in /proc/cpuinfo if someone is up to writing a patch. It could
>> also be useful to expose the PV features mask in cpuinfo too.
>>
>>
>
> What for? We already expose a QEMU cpu type that shows up in cpuinfo as so.
> All we'd have to do would be put the kvm information in the cpu type
> too. This would work
> in all kernels, without the need to patch.
>
What I'm talking about, is something like:
HypervisorPresent: yes
HypervisorType: KVM
Where HypervisorVendor could be KVM, Hyper-V, or ESX based on what the
cpuid leaf matched.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-01-31 21:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-31 12:19 Accessing pv_info from userland Bryan McLellan
2009-01-31 13:04 ` Glauber Costa
2009-01-31 19:36 ` Anthony Liguori
2009-01-31 19:55 ` Glauber Costa
2009-01-31 20:20 ` Bryan McLellan
2009-01-31 20:26 ` Glauber Costa
2009-01-31 21:08 ` Anthony Liguori [this message]
2009-01-31 21:18 ` Alexander Graf
2009-02-01 0:55 ` Anthony Liguori
2009-02-01 17:56 ` Alexander Graf
2009-02-03 10:50 ` Avi Kivity
2009-02-03 15:02 ` Glauber Costa
2009-02-04 14:16 ` Avi Kivity
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=4984BDE7.2060503@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=btm@loftninjas.org \
--cc=glommer@gmail.com \
--cc=kvm@vger.kernel.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.