From: Glauber Costa <glommer@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] add --accel option
Date: Wed, 29 Jul 2009 12:46:35 -0300 [thread overview]
Message-ID: <20090729154635.GD4776@poweredge.glommer> (raw)
In-Reply-To: <4A70055C.3050403@redhat.com>
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
next prev parent reply other threads:[~2009-07-29 15:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-28 20:48 [Qemu-devel] [PATCH] add --accel option Glauber Costa
2009-07-28 22:25 ` Filip Navara
2009-07-29 8:16 ` Kevin Wolf
2009-07-29 15:46 ` Glauber Costa [this message]
2009-07-29 15:46 ` Kevin Wolf
[not found] ` <m363db5vzj.fsf@neno.mitica>
2009-07-29 15:56 ` [Qemu-devel] " Kevin Wolf
2009-07-29 18:52 ` [Qemu-devel] " Paul Brook
2009-07-29 19:04 ` Anthony Liguori
-- strict thread matches above, loose matches on Subject: below --
2009-07-28 20:26 Glauber Costa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090729154635.GD4776@poweredge.glommer \
--to=glommer@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).