From: Cornelia Huck <cohuck@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] accel: Improve selection of the default accelerator
Date: Tue, 9 Oct 2018 17:06:28 +0200 [thread overview]
Message-ID: <20181009170628.7d453d90.cohuck@redhat.com> (raw)
In-Reply-To: <CAFEAcA9AfhifaHzGfNPwU7TG-4KUz0aO32utp86XWjHoHn3kUw@mail.gmail.com>
On Tue, 9 Oct 2018 15:34:22 +0100
Peter Maydell <peter.maydell@linaro.org> wrote:
> On 9 October 2018 at 15:23, Daniel P. Berrangé <berrange@redhat.com> wrote:
> > On Tue, Oct 09, 2018 at 02:58:41PM +0100, Peter Maydell wrote:
> >> On 9 October 2018 at 14:43, Cornelia Huck <cohuck@redhat.com> wrote:
> >> > I'm not sure why a single accelerator (any of them) would be a good
> >> > default. A list (tcg:kvm:<whatever>) sounds much saner, as it would
> >> > continue to work even if some accelerators have been disabled (right?)
> >> >
> >> > (And I'd prefer kvm to be first in that list; anything that relies on
> >> > tcg being used should specify it explicitly... a normal user will
> >> > likely always want the fast variant.)
> >>
> >> tcg should be the default for binaries without KVM compiled in,
> >> of course... But as Thomas points out, the reason for our current
> >> default is the usual "because we tend not to change things that
> >> would break existing working command lines".
> >
> > Putting KVM first shouldn't break existing working command lines
> > in general.
>
> There are ARM QEMU command lines which will fail with KVM
> and work with TCG (eg ones which use -cpu something-other-than-host
> or which ask for a GICv3 when the host has only a GICv2).
> These are basically cases where KVM can't provide features
> that TCG can. I imagine other archs like power have similar.
Well, on s390x there are (newer) cpu models that we don't support with
tcg but that work fine with kvm on a new-enough host... so I'm not sure
whether we can assume that any given accelerator supports the same set
of cpu models.
It feels like we're doomed whatever we decide to do :/
next prev parent reply other threads:[~2018-10-09 15:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 14:13 [Qemu-devel] [PATCH] accel: Improve selection of the default accelerator Thomas Huth
2018-10-05 14:22 ` Peter Maydell
2018-10-05 21:12 ` Paolo Bonzini
2018-10-10 8:02 ` Thomas Huth
2018-10-09 9:05 ` Markus Armbruster
2018-10-09 13:14 ` Markus Armbruster
2018-10-09 13:23 ` Thomas Huth
2018-10-09 13:41 ` Daniel P. Berrangé
2018-10-09 13:43 ` Cornelia Huck
2018-10-09 13:58 ` Peter Maydell
2018-10-09 14:23 ` Daniel P. Berrangé
2018-10-09 14:34 ` Peter Maydell
2018-10-09 15:06 ` Cornelia Huck [this message]
2018-10-09 15:35 ` Paolo Bonzini
2018-10-05 14:30 ` Cornelia Huck
2018-10-05 14:40 ` Peter Maydell
2018-10-05 21:13 ` Paolo Bonzini
2018-10-05 14:39 ` Philippe Mathieu-Daudé
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=20181009170628.7d453d90.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.