From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel <qemu-devel@nongnu.org>, Laszlo Ersek <lersek@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Cleber Rosa" <cleber@redhat.com>, "Oleg Vasilev" <me@svin.in>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Emilio Cota" <cota@braap.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
qemu-arm <qemu-arm@nongnu.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Idan Horowitz" <idan.horowitz@gmail.com>
Subject: Re: Analysis of slow distro boots in check-avocado (BootLinuxAarch64.test_virt_tcg*)
Date: Tue, 22 Feb 2022 16:17:23 +0000 [thread overview]
Message-ID: <878ru2nacq.fsf@linaro.org> (raw)
In-Reply-To: <874k4xbqvp.fsf@linaro.org>
Alex Bennée <alex.bennee@linaro.org> writes:
> Hi,
>
> TL;DR:
>
> - pc-bios/edk2-aarch64-code.fd should be rebuilt without debug
Laszlo,
Would it be possible to do a less debug enabled version of EDK2 on the
next update to pc-bios/edk2-*?
>
> So my working theory is:
>
> - booting with EFI leaves a number stale code pages
> - as the kernel boots it clears these pages triggering lots of
> slow-path writes
> - result very slow boot
>
> I think the only real solution is to improve our TB invalidation code
> but perhaps another approach would be to detect a high TB invalidation
> churn and just tb_flush the whole thing and start again?
>
> Any thoughts or ideas?
--
Alex Bennée
next prev parent reply other threads:[~2022-02-22 16:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 11:19 Analysis of slow distro boots in check-avocado (BootLinuxAarch64.test_virt_tcg*) Alex Bennée
2022-02-22 16:17 ` Alex Bennée [this message]
2022-02-22 16:38 ` Daniel P. Berrangé
2022-02-22 17:33 ` Philippe Mathieu-Daudé
2022-02-22 17:37 ` Peter Maydell
2022-02-22 18:05 ` Philippe Mathieu-Daudé
2022-02-23 8:48 ` Gerd Hoffmann
[not found] ` <87zgmhlwjw.fsf@linaro.org>
2022-02-23 10:58 ` Philippe Mathieu-Daudé
2022-02-23 9:19 ` Peter Maydell
2022-02-23 10:53 ` Philippe Mathieu-Daudé
2022-02-23 11:11 ` Daniel P. Berrangé
2022-02-23 11:50 ` Gerd Hoffmann
2022-02-24 9:10 ` Igor Mammedov
2022-02-24 11:39 ` Laszlo Ersek
2022-03-08 12:42 ` Gerd Hoffmann
2022-02-23 11:07 ` Daniel P. Berrangé
2022-02-23 13:34 ` Philippe Mathieu-Daudé
2022-02-23 13:43 ` Daniel P. Berrangé
2022-02-23 14:00 ` Philippe Mathieu-Daudé
2022-02-23 16:37 ` Laszlo Ersek
2022-02-23 19:28 ` 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=878ru2nacq.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=cleber@redhat.com \
--cc=cota@braap.org \
--cc=f4bug@amsat.org \
--cc=idan.horowitz@gmail.com \
--cc=lersek@redhat.com \
--cc=me@svin.in \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--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).