From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NZmXc-0004Il-Ox for qemu-devel@nongnu.org; Tue, 26 Jan 2010 09:37:16 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NZmXY-0004Di-Rv for qemu-devel@nongnu.org; Tue, 26 Jan 2010 09:37:16 -0500 Received: from [199.232.76.173] (port=43685 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NZmXY-0004DR-Jp for qemu-devel@nongnu.org; Tue, 26 Jan 2010 09:37:12 -0500 Received: from mx1.redhat.com ([209.132.183.28]:39951) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NZmXY-0002Rk-4d for qemu-devel@nongnu.org; Tue, 26 Jan 2010 09:37:12 -0500 Message-ID: <4B5EFE13.1070300@redhat.com> Date: Tue, 26 Jan 2010 16:37:07 +0200 From: Avi Kivity MIME-Version: 1.0 References: <20100126064902.GD25779@x200.localdomain> <03EA8701-C607-4B87-A6C6-1DCD3E5DCAAC@suse.de> <4B5EE9EF.6030904@codemonkey.ws> <197BDDDF-D808-4157-8270-42B72B99BE0D@suse.de> <4B5EED22.4080009@redhat.com> <4B5EF874.3080306@codemonkey.ws> <4B5EF903.1070508@redhat.com> <4B5EFAB6.4080102@codemonkey.ws> <4B5EFB7A.7010709@redhat.com> <4B5EFD18.1030008@codemonkey.ws> In-Reply-To: <4B5EFD18.1030008@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: KVM call agenda for Jan 26 List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Chris Wright , Alexander Graf , kvm@vger.kernel.org, qemu-devel@nongnu.org On 01/26/2010 04:32 PM, Anthony Liguori wrote: >>>> It would need to know which cpuid bits qemu supports. Only qemu >>>> knows that. >>> >>> I'm not sure I understand why. Can you elaborate? >>> >> >> If qemu doesn't recognize -cpu qemu64,+nx, then no amount of hardware >> and kvm.ko support will allow the user to enable nx in a guest. > > > Does -cpu host filter out flags that we don't know about? I'm pretty > sure it doesn't. Since we're planning on moving to -cpu host by > default for KVM, does it really matter? People who use discovery tools are probably setting up a migration cluster. They aren't going to use -cpu host. > > Oh, I was under the impression that the tool was meant to be software > agnostic. IOW, here are all the virt features your hardware supports. That's /proc/cpuinfo, we should just extend it, maybe that's what Alex meant, but I'd like to see something more capable. -- error compiling committee.c: too many arguments to function