From: Richard Henderson <richard.henderson@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>, qemu-devel@nongnu.org
Cc: qemu-arm@nongnu.org, "Peter Maydell" <peter.maydell@linaro.org>,
"Cleber Rosa" <crosa@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Beraldo Leal" <bleal@redhat.com>
Subject: Re: [RFC PATCH] tests/avocado: retire the Aarch64 TCG tests from boot_linux.py
Date: Fri, 3 Feb 2023 10:46:12 -1000 [thread overview]
Message-ID: <6be1085e-1909-45a3-741d-b2c8e1baaed0@linaro.org> (raw)
In-Reply-To: <20230203181632.2919715-1-alex.bennee@linaro.org>
On 2/3/23 08:16, Alex Bennée wrote:
> The two TCG tests for GICv2 and GICv3 are very heavy weight distros
> that take a long time to boot up, especially for an --enable-debug
> build. The total code coverage they give is:
>
> Overall coverage rate:
> lines......: 11.2% (59584 of 530123 lines)
> functions..: 15.0% (7436 of 49443 functions)
> branches...: 6.3% (19273 of 303933 branches)
>
> We already get pretty close to that with the machine_aarch64_virt
> tests which only does one full boot (~120s vs ~600s) of alpine. We
> expand the kernel+initrd boot (~8s) to test both GICs and also add an
> RNG device and a block device to generate a few IRQs and exercise the
> storage layer. With that we get to a coverage of:
>
> Overall coverage rate:
> lines......: 11.0% (58121 of 530123 lines)
> functions..: 14.9% (7343 of 49443 functions)
> branches...: 6.0% (18269 of 303933 branches)
>
> which I feel is close enough given the massive time saving. If we want
> to target any more sub-systems we can use lighter weight more directed
> tests.
>
> Signed-off-by: Alex Bennée<alex.bennee@linaro.org>
> Cc: Peter Maydell<peter.maydell@linaro.org>
> ---
> tests/avocado/boot_linux.py | 48 ++++----------------
> tests/avocado/machine_aarch64_virt.py | 63 ++++++++++++++++++++++++---
> 2 files changed, 65 insertions(+), 46 deletions(-)
Acked-by: Richard Henderson <richard.henderson@linaro.org>
r~
next prev parent reply other threads:[~2023-02-03 20:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 18:16 [RFC PATCH] tests/avocado: retire the Aarch64 TCG tests from boot_linux.py Alex Bennée
2023-02-03 20:35 ` Fabiano Rosas
2023-02-03 20:46 ` Richard Henderson [this message]
2023-02-10 16:05 ` 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=6be1085e-1909-45a3-741d-b2c8e1baaed0@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=bleal@redhat.com \
--cc=crosa@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=wainersm@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).