From: Thomas Huth <thuth@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>
Cc: Alex Bennee <alex.bennee@linaro.org>,
Claudio Fontana <cfontana@suse.de>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: does make check now require TCG? Or is it a parallelism issue?
Date: Fri, 9 Oct 2020 09:21:36 +0200 [thread overview]
Message-ID: <061f1bde-db0e-bc34-dae0-161606092bb0@redhat.com> (raw)
In-Reply-To: <CABgObfYWK2E8PsSFOcHpuA2vuA3HWgvtuLbrtQCWA=9=r07=5w@mail.gmail.com>
On 08/10/2020 20.24, Paolo Bonzini wrote:
>
>
> Il gio 8 ott 2020, 20:05 Richard Henderson <richard.henderson@linaro.org
> <mailto:richard.henderson@linaro.org>> ha scritto:
>
> Ah, TARGET_DIRS isn't being pruned anymore when a target is disabled for
> lack
> of accelerator.
>
> Paolo, side effect of 8a19980e3f ("configure: move accelerator logic to
> meson")? I guess we should move the setting of TARGET_DIRS to meson as
> well.
>
>
> TARGET_DIRS is pruned by Meson, I didn't add any back propagation to make
> because it is not really needed; qemu-iotests only every uses the "host
> architecture" QEMU binary (see tests/qemu-iotests/common.config),
> check-block + --target-list has never worked.
I haven't tried since the meson conversion, but at least a couple of months
ago, it was perfectly fine to run configure with
--target-list=tricore-softmmu and then to run "make check-block" afterwards.
That qemu_arch setting from tests/qemu-iotests/common.config is just used
for the preferred binary, but if it is not available,
tests/qemu-iotests/check falls back to any other qemu-system-xxx binary that
it can find.
Thomas
next prev parent reply other threads:[~2020-10-09 7:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 14:48 does make check now require TCG? Or is it a parallelism issue? Claudio Fontana
2020-10-08 15:02 ` Paolo Bonzini
2020-10-08 15:34 ` Claudio Fontana
2020-10-08 16:25 ` Claudio Fontana
2020-10-08 16:31 ` Paolo Bonzini
2020-10-08 16:35 ` Claudio Fontana
2020-10-08 16:51 ` Claudio Fontana
2020-10-09 9:23 ` Philippe Mathieu-Daudé
2020-10-09 9:40 ` Claudio Fontana
2020-10-09 10:35 ` Pavel Dovgalyuk
2020-10-09 11:46 ` Paolo Bonzini
2020-10-08 17:44 ` Richard Henderson
2020-10-08 17:53 ` Claudio Fontana
2020-10-08 18:05 ` Richard Henderson
2020-10-08 18:24 ` Paolo Bonzini
2020-10-08 21:07 ` Claudio Fontana
2020-10-09 7:40 ` Paolo Bonzini
2020-10-09 10:28 ` Claudio Fontana
2020-10-09 11:49 ` Paolo Bonzini
2020-10-09 12:13 ` Peter Maydell
2020-10-09 13:32 ` Claudio Fontana
2020-10-09 17:10 ` Paolo Bonzini
2020-10-09 7:21 ` Thomas Huth [this message]
2020-10-09 7:37 ` Paolo Bonzini
2020-10-09 9:25 ` 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=061f1bde-db0e-bc34-dae0-161606092bb0@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=cfontana@suse.de \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).