qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: "Fam Zheng" <fam@euphon.net>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	qemu-devel@nongnu.org,
	"David Gibson" <david@gibson.dropbear.id.au>
Subject: Re: [PATCH v1 4/4] .travis.yml: reduce the load on [ppc64] GCC check-tcg
Date: Mon, 04 May 2020 20:48:46 +0100	[thread overview]
Message-ID: <87r1vz5vmp.fsf@linaro.org> (raw)
In-Reply-To: <bfdd7881-c9e8-d058-52a8-1c88518b90fb@linaro.org>


Richard Henderson <richard.henderson@linaro.org> writes:

> On 5/3/20 7:10 PM, David Gibson wrote:
>>>>>           - TEST_CMD="make check check-tcg V=1"
>>>>> -        - CONFIG="--disable-containers --target-list=${MAIN_SOFTMMU_TARGETS},ppc64le-linux-user"
>>>>> +        - CONFIG="--disable-containers --target-list=ppc64-softmmu,ppc64le-linux-user"
>>>>
>>>> Cc'ing David, since I'm not sure about this one... Maybe split as we
>>>> did with other jobs?
> ...
>> Hrm.  I'd prefer not to drop this coverage if we can avoid it.  What
>> we're not testing with the proposed patch is TCG generation for a ppc
>> host but a non-ppc target.  e.g. if the x86 or ARM target side generates
>> some pattern of TCG ops that's very rare for the ppc target, and is
>> buggy in the ppc host side.
>
> Are we actually testing those here?  As far as I can see, we're not installing
> any cross-compilers here, so we're not building any non-ppc binaries.  Nor are
> we running check-acceptance which would download pre-built foreign
> binaries.

We are testing the very minimal boot stubs that each -system binary has
in qtest but they are hardly going to be exercising the majority of the
TCG. Basically the $SELF-linux-user is going to be exercising more of
the TCG than anything else.

>
>
> r~


-- 
Alex Bennée


  reply	other threads:[~2020-05-04 19:50 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-01 11:15 [PATCH v1 0/4] testing/next updates Alex Bennée
2020-05-01 11:15 ` [PATCH v1 1/4] .travis.yml: show free disk space at end of run Alex Bennée
2020-05-01 12:18   ` Philippe Mathieu-Daudé
2020-05-01 11:15 ` [PATCH v1 2/4] .travis.yml: drop MacOSX Alex Bennée
2020-05-01 11:21   ` Daniel P. Berrangé
2020-05-01 15:03     ` Alex Bennée
2020-05-04 19:50     ` Alex Bennée
2020-05-01 12:19   ` Philippe Mathieu-Daudé
2020-05-01 14:25   ` Richard Henderson
2020-05-01 11:15 ` [PATCH v1 3/4] .cirrus.yml: bump FreeBSD to the current stable release Alex Bennée
2020-05-04 10:26   ` Li-Wen Hsu
2020-05-06  8:16     ` Alex Bennée
2020-05-01 11:15 ` [PATCH v1 4/4] .travis.yml: reduce the load on [ppc64] GCC check-tcg Alex Bennée
2020-05-01 12:23   ` Philippe Mathieu-Daudé
2020-05-01 12:58     ` Alex Bennée
2020-05-04  2:10       ` David Gibson
2020-05-04 17:39         ` Richard Henderson
2020-05-04 19:48           ` Alex Bennée [this message]
2020-05-05  0:40             ` David Gibson
2020-05-01 14:30   ` Richard Henderson
2020-05-01 11:23 ` [PATCH v1 0/4] testing/next updates Daniel P. Berrangé
2020-05-01 11:34   ` Alex Bennée
2020-05-01 12:22   ` Philippe Mathieu-Daudé
2020-05-01 11:36 ` no-reply
2020-05-01 13:11 ` no-reply

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=87r1vz5vmp.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=david@gibson.dropbear.id.au \
    --cc=fam@euphon.net \
    --cc=philmd@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).