From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mvttu-00066S-CR for qemu-devel@nongnu.org; Thu, 08 Oct 2009 10:23:26 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mvttp-00064M-Ol for qemu-devel@nongnu.org; Thu, 08 Oct 2009 10:23:26 -0400 Received: from [199.232.76.173] (port=37947 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mvttp-000648-J1 for qemu-devel@nongnu.org; Thu, 08 Oct 2009 10:23:21 -0400 Received: from mail-fx0-f214.google.com ([209.85.220.214]:55105) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mvtto-0006s5-Mr for qemu-devel@nongnu.org; Thu, 08 Oct 2009 10:23:21 -0400 Received: by fxm10 with SMTP id 10so5598576fxm.8 for ; Thu, 08 Oct 2009 07:23:19 -0700 (PDT) Message-ID: <4ACDF5D2.2070408@codemonkey.ws> Date: Thu, 08 Oct 2009 09:23:14 -0500 From: Anthony Liguori 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> <4ACDF233.3090500@redhat.com> In-Reply-To: <4ACDF233.3090500@redhat.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: Avi Kivity Cc: Andre Przywara , Anthony Liguori , Gerd Hoffmann , Glauber Costa , qemu-devel@nongnu.org Avi Kivity wrote: > 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=. If we make the kvm device a separate device, then it's about choosing which device to use. Regardless, even if it were a single device, it's still a property of the device so a qdev property would be the logical way to expose it. >> 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. They are different device models that happen to implement the same guest-visible device. Regards, Anthony Liguori