From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NZmJl-0005lA-2Y for qemu-devel@nongnu.org; Tue, 26 Jan 2010 09:22:57 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NZmJg-0005gF-2Z for qemu-devel@nongnu.org; Tue, 26 Jan 2010 09:22:56 -0500 Received: from [199.232.76.173] (port=60110 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NZmJf-0005fu-L4 for qemu-devel@nongnu.org; Tue, 26 Jan 2010 09:22:51 -0500 Received: from mail-gx0-f223.google.com ([209.85.217.223]:42513) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NZmJf-0000Wi-CT for qemu-devel@nongnu.org; Tue, 26 Jan 2010 09:22:51 -0500 Received: by gxk23 with SMTP id 23so5606586gxk.2 for ; Tue, 26 Jan 2010 06:22:50 -0800 (PST) Message-ID: <4B5EFAB6.4080102@codemonkey.ws> Date: Tue, 26 Jan 2010 08:22:46 -0600 From: Anthony Liguori 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> In-Reply-To: <4B5EF903.1070508@redhat.com> 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: Avi Kivity Cc: Chris Wright , Alexander Graf , kvm@vger.kernel.org, qemu-devel@nongnu.org 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? Regards, Anthony Liguori