From: Thomas Huth <thuth@redhat.com>
To: "Markus Armbruster" <armbru@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Laurent Vivier" <lvivier@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH] tests: improve performance of device-introspect-test
Date: Sun, 12 Jul 2020 20:43:58 +0200 [thread overview]
Message-ID: <c353a610-6989-331c-cb65-a893602a376a@redhat.com> (raw)
In-Reply-To: <87mu47gms3.fsf@dusky.pond.sub.org>
On 10/07/2020 22.03, Markus Armbruster wrote:
[...]
> With -m slow, we test 2 * #machines * #devices introspections,
> i.e. from 132 (tricore) to over 10k (ppc 13046, ppc64 23426, arm
> 82708, aarch64 89760). Median is ~1600, sum is ~260k.
>
> Except we actually test just 89k now, because the test *fails* for arm
> and aarch64 after some 500 introspections: introspecting device
> msf2-soc with machine ast2600-evb makes QEMU terminate unsuccessfully
> with "Unsupported NIC model: ftgmac100". Cause: m2sxxx_soc_initfn()
> calls qemu_check_nic_model(). Goes back to commit 05b7374a58 "msf2:
> Add EMAC block to SmartFusion2 SoC", merged some ten weeks ago. This
> is exactly the kind of mistake the test is designed to catch. How
> come it wasn't? Possibly due to unlucky combination with the slowdown
> discussed in the next item (but that was less than four weeks ago).
Well, the explanation is simpler: Nobody ran the
device-introspection-test with the arm target in slow mode! Hardly
anybody runs the tests with SPEED=slow, and in the CI, we currently only
run the test in slow mode for the i386-softmmu, ppc64-softmmu and
mips64-softmmu targets. Simply because testing with arm was toooo slow
when I wrote that CI script, I didn't want to wait endlessly here.
But now with the speedup patch from Daniel, and maybe with some smarter
checks in the YML file (I now know that there are things like "only:
changes:" keywords so we could e.g. only run that test if something in
hw/arm/* has changed), I think it should be feasible to get this
included in the CI, too.
Thomas
next prev parent reply other threads:[~2020-07-12 18:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 11:28 [PATCH] tests: improve performance of device-introspect-test Daniel P. Berrangé
2020-07-09 11:44 ` Laurent Vivier
2020-07-09 11:59 ` Daniel P. Berrangé
2020-07-09 12:14 ` Laurent Vivier
2020-07-09 16:18 ` Markus Armbruster
2020-07-10 20:03 ` Markus Armbruster
2020-07-12 18:43 ` Thomas Huth [this message]
2020-07-13 8:47 ` Daniel P. Berrangé
2020-07-14 7:57 ` Markus Armbruster
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=c353a610-6989-331c-cb65-a893602a376a@redhat.com \
--to=thuth@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--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).