From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: KVM call agenda for Jan 26 Date: Tue, 26 Jan 2010 08:32:56 -0600 Message-ID: <4B5EFD18.1030008@codemonkey.ws> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Alexander Graf , Chris Wright , kvm@vger.kernel.org, qemu-devel@nongnu.org To: Avi Kivity Return-path: Received: from mail-gx0-f224.google.com ([209.85.217.224]:40979 "EHLO mail-gx0-f224.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754350Ab0AZOdP (ORCPT ); Tue, 26 Jan 2010 09:33:15 -0500 Received: by gxk24 with SMTP id 24so5777176gxk.1 for ; Tue, 26 Jan 2010 06:33:15 -0800 (PST) In-Reply-To: <4B5EFB7A.7010709@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 01/26/2010 08:26 AM, Avi Kivity wrote: > On 01/26/2010 04:22 PM, Anthony Liguori wrote: >> On 01/26/2010 08:15 AM, Avi Kivity wrote: >>> On 01/26/2010 04:13 PM, Anthony Liguori wrote: >>>>> Me too, especially as the whole stack is involved, and qemu is the >>>>> topmost part from our perspective (no doubt libvirt will want to >>>>> integrate that functionality as well). >>>> >>>> >>>> I'm not sure I agree. It would use no code from qemu and really >>>> benefit in no way from being part of qemu. I don't feel that >>>> strongly about it though. >>>> >>> >>> 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? 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. Regards, Anthony Liguori