qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Helge Deller <deller@gmx.de>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] configure: Automatically fall back to TCI on non-release architectures
Date: Fri, 5 Apr 2019 08:34:26 +0700	[thread overview]
Message-ID: <CAFEAcA9xP8CtXEruuzPHCyuDT5EyMMHFGdCJdfFBhX+C2Jr36A@mail.gmail.com> (raw)
In-Reply-To: <20190404185730.GA22512@ls3530.dellerweb.de>

On Fri, 5 Apr 2019 at 01:59, Helge Deller <deller@gmx.de> wrote:
> If a non-release architecture is found, and it's known that there is no
> native TCG support for that CPU, automatically fall back to the TCI
> implementation instead of requesting the user to run configure again
> with the --enable-tcg-interpreter option.
>
> This change simplifies building qemu in automatic build environments
> (like in my case the debian buildds) because one does not need to
> special case on the architectures.

I don't think we should do this. TCI is unmaintained, has several
known flaws, does not provide the level of performance that
people expect from QEMU, and we've talked about removing it
altogether. In particular, distros should not automatically ship
a TCI QEMU -- it's something that a user can use if they
explicitly opt into but which I don't think we want to surprise
anybody with.

If we care about a host architecture we should support it
with a proper TCG backend. If we don't care that much we
shouldn't support it.

thanks
-- PMM

  parent reply	other threads:[~2019-04-05  1:34 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-04 18:57 [Qemu-devel] [PATCH] configure: Automatically fall back to TCI on non-release architectures Helge Deller
2019-04-04 19:24 ` Philippe Mathieu-Daudé
2019-04-05  7:14   ` Helge Deller
2019-04-05  7:14     ` Helge Deller
2019-04-05  1:34 ` Peter Maydell [this message]
2019-04-05  1:34   ` Peter Maydell
2019-04-05  7:56   ` Helge Deller
2019-04-05  7:56     ` Helge Deller
2019-04-05  8:26     ` Daniel P. Berrangé
2019-04-05  8:26       ` Daniel P. Berrangé
2019-04-05  9:02       ` Helge Deller
2019-04-05  9:02         ` Helge Deller
2019-04-05  9:10         ` Philippe Mathieu-Daudé
2019-04-05  9:10           ` Philippe Mathieu-Daudé
2019-04-05  9:13         ` Peter Maydell
2019-04-05  9:13           ` Peter Maydell
2019-04-05  9:15         ` Daniel P. Berrangé
2019-04-05  9:15           ` Daniel P. Berrangé
2019-04-05  8:47     ` Philippe Mathieu-Daudé
2019-04-05  8:47       ` Philippe Mathieu-Daudé
2019-04-05  9:02       ` Daniel P. Berrangé
2019-04-05  9:02         ` Daniel P. Berrangé
2019-04-05  9:16         ` Philippe Mathieu-Daudé
2019-04-05  9:16           ` Philippe Mathieu-Daudé
2019-04-09 19:46           ` Stefan Weil
2019-04-09 19:46             ` Stefan Weil
2019-04-09 20:39             ` Richard Henderson
2019-04-09 20:39               ` Richard Henderson
2019-04-10  6:17               ` Stefan Weil
2019-04-10  6:17                 ` Stefan Weil
2019-04-11  6:21                 ` Richard Henderson
2019-04-11  6:21                   ` Richard Henderson
2019-04-10  6:07             ` Thomas Huth
2019-04-10  6:07               ` Thomas Huth
2019-04-10  6:24               ` Stefan Weil
2019-04-10  6:24                 ` Stefan Weil
2019-04-10  8:22               ` Thomas Huth
2019-04-10  8:22                 ` Thomas Huth
2019-04-10 19:22                 ` Stefan Weil
2019-04-10 19:22                   ` Stefan Weil
2019-04-10  7:48             ` Thomas Huth
2019-04-10  7:48               ` Thomas Huth
2019-04-06  8:59     ` Richard Henderson
2019-04-06  8:59       ` Richard Henderson

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=CAFEAcA9xP8CtXEruuzPHCyuDT5EyMMHFGdCJdfFBhX+C2Jr36A@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=deller@gmx.de \
    --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).