From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Accessing pv_info from userland Date: Wed, 04 Feb 2009 16:16:21 +0200 Message-ID: <4989A335.6020303@redhat.com> References: <893823750901310419q63e9b648u9c959bc2689ef94d@mail.gmail.com> <5d6222a80901310504x76363751p9c28a63a3f01530@mail.gmail.com> <4984A825.3020904@codemonkey.ws> <5d6222a80901311155l2c20fa0aw8cabdac5e6f3caaa@mail.gmail.com> <49882193.3010801@redhat.com> <5d6222a80902030702k4354f75eoc49f3d03fe98629c@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Anthony Liguori , Bryan McLellan , kvm@vger.kernel.org To: Glauber Costa Return-path: Received: from mx2.redhat.com ([66.187.237.31]:47787 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751598AbZBDOQa (ORCPT ); Wed, 4 Feb 2009 09:16:30 -0500 In-Reply-To: <5d6222a80902030702k4354f75eoc49f3d03fe98629c@mail.gmail.com> Sender: kvm-owner@vger.kernel.org List-ID: Glauber Costa wrote: > On Tue, Feb 3, 2009 at 8:50 AM, Avi Kivity wrote: > >> Glauber Costa wrote: >> >>> 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. >>> >>> >> For client virtualization (no migration) we'll want to support a mode where >> we let the guest see the host cpuid (or as much of it as we can). >> > > And how exactly does that invalidate what I've said ? > You'll want to expose AuthenticIntel or GenuineAMD (with the full cpu brand string) in this model. So no TheOneTrueQEMU cpu type. > As we can select the cpu type, we can easily pick one that expose as > much of the underlying cpu > as possible. > This includes the cpu type... Hypervisor presence and type is in addition to the cpu type, not a replacement. -- error compiling committee.c: too many arguments to function