From: Thomas Huth <thuth@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
qemu-block@nongnu.org, "Markus Armbruster" <armbru@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
qemu-devel@nongnu.org, "Max Reitz" <mreitz@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: Priority of -accel (was: [PATCH] tests/qemu-iotests: Update tests to recent desugarized -accel option)
Date: Tue, 7 Jan 2020 15:14:52 +0100 [thread overview]
Message-ID: <3241dff4-6223-404f-55d4-846991763046@redhat.com> (raw)
In-Reply-To: <20200107125451.GL3368802@redhat.com>
On 07/01/2020 13.54, Daniel P. Berrangé wrote:
> On Tue, Jan 07, 2020 at 01:23:18PM +0100, Paolo Bonzini wrote:
>> On 07/01/20 13:18, Thomas Huth wrote:
>>> I don't think we need a separate priority parameter here. But IMHO it's
>>> really rather common practice to prioritize the last option. So while
>>> it might be more "self-explanatory" to a CLI newbie if the first
>>> occurrence got the highest priority, it might be rather confusing
>>> instead for a CLI veteran...?
>>
>> Prioritising the last certainly makes sense for a choose-one-only
>> option, but I'm not sure it's the same for a choose-best option. After
>> all it was -machine accel=kvm:tcg, not -machine accel=tcg:kvm...
>
> IIUC, the main use case for specifying multiple accelerators is
> so that lazy invokations can ask for a hardware virt, but then get
> fallback to TCG if not available. For things that should be platform
> portabile, there's more than just kvm to consider though, as we have
> many accelerators. Listing all possible accelerators is kind of
> crazy though no matter what the syntax is.
>
> How about taking a completely different approach, inspired by the
> -cpu arg and implement:
>
> -machine accel=best
Something like that sounds like the best solution to me, but I'd maybe
rather not call it "best", since the definition of "best" might depend
on your use-case (e.g. do you want to use a CPU close to the host or
something different which might be better emulated by TCG?).
What about "-accel any" or "-accel fastest" or something similar?
Thomas
next prev parent reply other threads:[~2020-01-07 15:03 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 [this message]
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é
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=3241dff4-6223-404f-55d4-846991763046@redhat.com \
--to=thuth@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@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=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).