From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Oleg Vasilev" <me@svin.in>,
"Idan Horowitz" <idan.horowitz@gmail.com>,
"Cleber Rosa" <cleber@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Emilio Cota" <cota@braap.org>,
"Gerd Hoffmann" <kraxel@redhat.com>,
qemu-arm <qemu-arm@nongnu.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Laszlo Ersek" <lersek@redhat.com>
Subject: Re: Analysis of slow distro boots in check-avocado (BootLinuxAarch64.test_virt_tcg*)
Date: Tue, 22 Feb 2022 16:38:22 +0000 [thread overview]
Message-ID: <YhURfqMvRT4xbiz6@redhat.com> (raw)
In-Reply-To: <878ru2nacq.fsf@linaro.org>
On Tue, Feb 22, 2022 at 04:17:23PM +0000, Alex Bennée wrote:
>
> 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-*?
NB, Laszlo is no longer maintaining EDK2 in QEMU, it was handed
over to Philippe. I'm CC'ing Gerd too since he's a reviewer and
an EDK2 contributor taking over from Lazslo in EDK2 community
>
> >
> > 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
>
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2022-02-22 17:07 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
2022-02-22 16:38 ` Daniel P. Berrangé [this message]
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=YhURfqMvRT4xbiz6@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=cleber@redhat.com \
--cc=cota@braap.org \
--cc=f4bug@amsat.org \
--cc=idan.horowitz@gmail.com \
--cc=kraxel@redhat.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).