From: Peter Maydell <peter.maydell@linaro.org>
To: Thomas Huth <thuth@redhat.com>
Cc: "Daniel P. Berrange" <berrange@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
"patches@linaro.org" <patches@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <rth@twiddle.net>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH] configure: Warn about deprecated hosts
Date: Fri, 17 Mar 2017 13:25:17 +0000 [thread overview]
Message-ID: <CAFEAcA8R1bf6kRB6L=uyQAoQJBPaDxK7pG2C-9ApW9BLdR_oiw@mail.gmail.com> (raw)
In-Reply-To: <95e695ba-3ecc-5254-721e-b35ed08b8074@redhat.com>
On 17 March 2017 at 13:19, Thomas Huth <thuth@redhat.com> wrote:
> So could you maybe change your patch that it does not warn when the user
> has run configure with the "--enable-tcg-interpreter" option?
Nope. I specifically don't want to enable support for TCI on random
who-knows-what-this-is architectures. It eats up too much time
causing people to worry about "what if this is some weird thing"
when they're trying to refactor code, when in practice nobody
is really using QEMU on oddball host CPUs.
If somebody wants to support QEMU as a TCI-only setup on a
new host architecture, they can submit a patch to configure
that specifically recognizes the host architecture (even
if we don't have a tcg backend for it).
thanks
-- PMM
next prev parent reply other threads:[~2017-03-17 13:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-17 11:08 [Qemu-devel] [PATCH] configure: Warn about deprecated hosts Peter Maydell
2017-03-17 11:49 ` Daniel P. Berrange
2017-03-17 11:52 ` Peter Maydell
2017-03-17 11:56 ` Daniel P. Berrange
2017-03-17 13:10 ` Andrea Bolognani
2017-03-17 13:19 ` Thomas Huth
2017-03-17 13:22 ` Peter Maydell
2017-03-17 13:50 ` Thomas Huth
2017-03-17 13:25 ` Peter Maydell [this message]
2017-03-17 23:15 ` Richard Henderson
2017-03-17 12:38 ` Andrew Jones
2017-03-17 15:19 ` Peter Maydell
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='CAFEAcA8R1bf6kRB6L=uyQAoQJBPaDxK7pG2C-9ApW9BLdR_oiw@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=aurelien@aurel32.net \
--cc=berrange@redhat.com \
--cc=patches@linaro.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--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 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).