From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: Accessing pv_info from userland Date: Sat, 31 Jan 2009 15:08:55 -0600 Message-ID: <4984BDE7.2060503@codemonkey.ws> References: <893823750901310419q63e9b648u9c959bc2689ef94d@mail.gmail.com> <5d6222a80901310504x76363751p9c28a63a3f01530@mail.gmail.com> <4984A825.3020904@codemonkey.ws> <5d6222a80901311155l2c20fa0aw8cabdac5e6f3caaa@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Bryan McLellan , kvm@vger.kernel.org To: Glauber Costa Return-path: Received: from an-out-0708.google.com ([209.85.132.240]:23185 "EHLO an-out-0708.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754946AbZAaVJX (ORCPT ); Sat, 31 Jan 2009 16:09:23 -0500 Received: by an-out-0708.google.com with SMTP id c2so405880anc.1 for ; Sat, 31 Jan 2009 13:09:21 -0800 (PST) In-Reply-To: <5d6222a80901311155l2c20fa0aw8cabdac5e6f3caaa@mail.gmail.com> Sender: kvm-owner@vger.kernel.org List-ID: Glauber Costa wrote: > On Sat, Jan 31, 2009 at 5:36 PM, Anthony Liguori 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