Re: Accessing pv_info from userland

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 31.01.2009, at 22:08, Anthony Liguori <anthony@xxxxxxxxxxxxx> wrote:

Glauber Costa wrote:
On Sat, Jan 31, 2009 at 5:36 PM, Anthony Liguori <anthony@xxxxxxxxxxxxx > 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

Why not rather do

Platform: native

Or

Platform: KVM

So things stay consistent :)

Alex



Where HypervisorVendor could be KVM, Hyper-V, or ESX based on what the cpuid leaf matched.

Regards,

Anthony Liguori
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux