From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>, "Thomas Huth" <thuth@redhat.com>,
qemu-block@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel@nongnu.org,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Max Reitz" <mreitz@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: Priority of -accel (was: [PATCH] tests/qemu-iotests: Update tests to recent desugarized -accel option)
Date: Wed, 8 Jan 2020 13:10:15 +0000 [thread overview]
Message-ID: <20200108131015.GF3386452@redhat.com> (raw)
In-Reply-To: <60ecc0ec-d8db-2cf6-b21a-799f4cb9ab71@redhat.com>
On Wed, Jan 08, 2020 at 01:41:59PM +0100, Paolo Bonzini wrote:
> On 08/01/20 11:58, Thomas Huth wrote:
> >> "-accel default" could be considered to have vibes of Do The Right
> >> Thing (tm) and could in time actually become so!
> >
> > "-accel default" sounds like the default behavior that you'd also get if
> > you don't use this option at all ... what about "-accel auto" to say
> > that QEMU should pick an accelerator automatically?
>
> Questions to answer before thinking about the name: how would it
> co-operate with other "-accel" options? how would you pass sub-options
> to the accelerators?
If people don't have a preference for a specific accelerator, just need
"a working accelerator", then I think it is reasonable to assume they
won't want/need to pass options to the accelerators either.
"-accel default" is targetting the simple "do the right thing" use
case, so IMHO doesn't need to support per-accelerator options.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2020-01-08 13:11 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 13:09 [PATCH] tests/qemu-iotests: Update tests to recent desugarized -accel option Philippe Mathieu-Daudé
2020-01-06 13:16 ` Max Reitz
2020-01-07 10:03 ` Priority of -accel (was: [PATCH] tests/qemu-iotests: Update tests to recent desugarized -accel option) Thomas Huth
2020-01-07 10:14 ` Paolo Bonzini
2020-01-07 12:18 ` Thomas Huth
2020-01-07 12:23 ` Paolo Bonzini
2020-01-07 12:54 ` Daniel P. Berrangé
2020-01-07 14:14 ` Thomas Huth
2020-01-07 14:20 ` Priority of -accel Philippe Mathieu-Daudé
2020-01-07 14:27 ` Daniel P. Berrangé
2020-01-07 14:35 ` Thomas Huth
2020-01-13 14:39 ` Markus Armbruster
2020-01-13 16:14 ` Christophe de Dinechin
2020-01-13 16:23 ` Paolo Bonzini
2020-01-07 14:26 ` Priority of -accel (was: [PATCH] tests/qemu-iotests: Update tests to recent desugarized -accel option) Daniel P. Berrangé
2020-01-08 10:39 ` Alex Bennée
2020-01-08 10:58 ` Thomas Huth
2020-01-08 12:41 ` Paolo Bonzini
2020-01-08 13:10 ` Daniel P. Berrangé [this message]
2020-01-08 13:24 ` Paolo Bonzini
2020-01-08 14:00 ` Priority of -accel Thomas Huth
2020-01-08 11:00 ` Priority of -accel (was: [PATCH] tests/qemu-iotests: Update tests to recent desugarized -accel option) Peter Maydell
2020-01-10 10:43 ` Peter Maydell
2020-01-07 12:29 ` Kevin Wolf
2020-01-07 12:34 ` Priority of -accel Philippe Mathieu-Daudé
2020-01-07 12:37 ` Philippe Mathieu-Daudé
2020-01-07 13:55 ` Priority of -accel (was: [PATCH] tests/qemu-iotests: Update tests to recent desugarized -accel option) Christophe de Dinechin
2020-01-07 14:37 ` Paolo Bonzini
2020-01-07 14:42 ` Thomas Huth
2020-01-07 17:43 ` Christophe de Dinechin
2020-01-07 17:53 ` Peter Maydell
2020-01-08 9:47 ` Kevin Wolf
2020-01-13 16:17 ` Priority of -accel Markus Armbruster
2020-01-13 16:25 ` Paolo Bonzini
2020-01-14 8:59 ` Markus Armbruster
2020-01-14 10:44 ` Paolo Bonzini
2020-01-14 17:49 ` Christophe de Dinechin
2020-01-14 17:59 ` Daniel P. Berrangé
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=20200108131015.GF3386452@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
/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).