From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mvtew-00070w-Dk for qemu-devel@nongnu.org; Thu, 08 Oct 2009 10:07:58 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mvteq-0006qD-P4 for qemu-devel@nongnu.org; Thu, 08 Oct 2009 10:07:56 -0400 Received: from [199.232.76.173] (port=49308 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mvteq-0006pb-FZ for qemu-devel@nongnu.org; Thu, 08 Oct 2009 10:07:52 -0400 Received: from mx1.redhat.com ([209.132.183.28]:5528) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mvtep-0003lS-Ol for qemu-devel@nongnu.org; Thu, 08 Oct 2009 10:07:52 -0400 Message-ID: <4ACDF233.3090500@redhat.com> Date: Thu, 08 Oct 2009 16:07:47 +0200 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: [PATCH v2 9/9] Add -kvm option References: <1254953315-5761-1-git-send-email-glommer@redhat.com> <1254953315-5761-2-git-send-email-glommer@redhat.com> <1254953315-5761-3-git-send-email-glommer@redhat.com> <1254953315-5761-4-git-send-email-glommer@redhat.com> <1254953315-5761-5-git-send-email-glommer@redhat.com> <1254953315-5761-6-git-send-email-glommer@redhat.com> <1254953315-5761-7-git-send-email-glommer@redhat.com> <1254953315-5761-8-git-send-email-glommer@redhat.com> <1254953315-5761-9-git-send-email-glommer@redhat.com> <1254953315-5761-10-git-send-email-glommer@redhat.com> <4ACD1D92.8080607@us.ibm.com> In-Reply-To: <4ACD1D92.8080607@us.ibm.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Andre Przywara , Glauber Costa , qemu-devel@nongnu.org, Gerd Hoffmann On 10/08/2009 01:00 AM, Anthony Liguori wrote: > Glauber Costa wrote: >> This option deprecates --enable-kvm. It is a more flexible option, >> that makes use of qemu-opts, and allow us to pass on options to >> enable or >> disable kernel irqchip, for example. > > With proper qdev support, you could select kvm device models based on > -device so I think this option isn't all that useful. qdev (mostly?) is about the guest interface; this is more about the host implementation, so akin to -drive file= and cache=. > What I'd like to see in the interim is a kvm specific machine type > that's defaulted to if kvm is enabled. I think this would be useful > not only for enabling things like in-kernel apic, but also for > selecting a default cpu model. We should make a distinction between guest-visible changes and accelerators like kvm-irqchip and vhost. -- error compiling committee.c: too many arguments to function