From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MWBFm-0004xD-HF for qemu-devel@nongnu.org; Wed, 29 Jul 2009 11:39:42 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MWBFh-0004t2-PP for qemu-devel@nongnu.org; Wed, 29 Jul 2009 11:39:42 -0400 Received: from [199.232.76.173] (port=58713 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MWBFh-0004su-IX for qemu-devel@nongnu.org; Wed, 29 Jul 2009 11:39:37 -0400 Received: from mx2.redhat.com ([66.187.237.31]:37769) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MWBFg-0003Nd-Sq for qemu-devel@nongnu.org; Wed, 29 Jul 2009 11:39:37 -0400 Date: Wed, 29 Jul 2009 12:46:35 -0300 From: Glauber Costa Subject: Re: [Qemu-devel] [PATCH] add --accel option Message-ID: <20090729154635.GD4776@poweredge.glommer> References: <1248814081-7860-1-git-send-email-glommer@redhat.com> <4A70055C.3050403@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A70055C.3050403@redhat.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Kevin Wolf Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org On Wed, Jul 29, 2009 at 10:16:28AM +0200, Kevin Wolf wrote: > Glauber Costa schrieb: > > Since libvirt dudes seem to prefer it, add a --accel option. For now, > > it only does the same as --enable-kvm, but it can easily be extended > > in the future. It also accepts "none" and "kqemu" options. > > The documentation should include which values are valid for the option. > Guessing that the syntax is -accel kvm is probably possible, but for > -accel kqemu,mode=kernel it's definitely hard. right now kqemu needs an extra argument. But very soon kvm will need it too. Like for example controlling knobs like kvm-irqchip and kvm-pit. So maybe we want a standard way of passing arguments for all accels? How about --accel foo,args=bar,bar,bar with the args part being optional ? An exampel would be --accel kvm,args=userpit,userirqchip (assuming we want the default to be in the kernel) Otherwise we're stuck with an evergrowing combination to support