From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [kvm-devel] Re: expose host CPU features to guests Date: Sun, 09 Sep 2007 18:29:16 +0300 Message-ID: <46E4114C.6090804@qumranet.com> References: <20070905174530.GA3945@karma.qumranet.com> <46E3ED2B.6080606@qumranet.com> <20070909130725.GF24240@mail.shareable.org> <200709091625.59859.paul@codesourcery.com> Reply-To: qemu-devel@nongnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm-devel , qemu-devel@nongnu.org To: Paul Brook Return-path: In-Reply-To: <200709091625.59859.paul@codesourcery.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org List-Id: kvm.vger.kernel.org Paul Brook wrote: > On Sunday 09 September 2007, Jamie Lokier wrote: > >> Avi Kivity wrote: >> >>> Let's start with '-cpu host' as 'cpu host-cpuid' and implement '-cpu >>> host-os' on the first bug report? I have a feeling we won't ever see it. >>> >> In other words, host-os is what _I'd_ implement because I care too >> much about the poor obscure users and think it's the safe option, but >> I'm not doing the implementing here ;-) >> > > I agree. If the host OS has disabled a feature, it's a fair bet it's done that > for a reason. > > The reason may not be relevant to the guest. > What you really want to do is ask your virtualization module what features it > supports. > Yes, that needs to be an additional filter. -- error compiling committee.c: too many arguments to function From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IUOj1-0004uR-CU for qemu-devel@nongnu.org; Sun, 09 Sep 2007 11:29:27 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IUOix-0004tR-0z for qemu-devel@nongnu.org; Sun, 09 Sep 2007 11:29:27 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IUOiw-0004tD-Fd for qemu-devel@nongnu.org; Sun, 09 Sep 2007 11:29:22 -0400 Received: from il.qumranet.com ([82.166.9.18]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IUOiw-0007EN-1w for qemu-devel@nongnu.org; Sun, 09 Sep 2007 11:29:22 -0400 Message-ID: <46E4114C.6090804@qumranet.com> Date: Sun, 09 Sep 2007 18:29:16 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [kvm-devel] [Qemu-devel] Re: expose host CPU features to guests References: <20070905174530.GA3945@karma.qumranet.com> <46E3ED2B.6080606@qumranet.com> <20070909130725.GF24240@mail.shareable.org> <200709091625.59859.paul@codesourcery.com> In-Reply-To: <200709091625.59859.paul@codesourcery.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paul Brook Cc: kvm-devel , qemu-devel@nongnu.org Paul Brook wrote: > On Sunday 09 September 2007, Jamie Lokier wrote: > >> Avi Kivity wrote: >> >>> Let's start with '-cpu host' as 'cpu host-cpuid' and implement '-cpu >>> host-os' on the first bug report? I have a feeling we won't ever see it. >>> >> In other words, host-os is what _I'd_ implement because I care too >> much about the poor obscure users and think it's the safe option, but >> I'm not doing the implementing here ;-) >> > > I agree. If the host OS has disabled a feature, it's a fair bet it's done that > for a reason. > > The reason may not be relevant to the guest. > What you really want to do is ask your virtualization module what features it > supports. > Yes, that needs to be an additional filter. -- error compiling committee.c: too many arguments to function