From: "Ard Biesheuvel" <ardb@kernel.org>
To: edk2-devel-groups-io <devel@edk2.groups.io>, chris.willing@linux.com
Subject: Re: [edk2-devel] [PATCH 1/1] OvmfPkg PlatformBootManagerLib: Move TryRunningQemuKernel()
Date: Mon, 9 Aug 2021 15:08:45 +0200 [thread overview]
Message-ID: <CAMj1kXHT61zi=eDsObZZaEV7A0g1B3YEkZ6DVjRouvqDN=_bEA@mail.gmail.com> (raw)
In-Reply-To: <20210728020232.127332-2-chris.willing@linux.com>
On Wed, 28 Jul 2021 at 04:18, Christoph Willing <chris.willing@linux.com> wrote:
>
> Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=3504
>
> This change ensures that PlatformBdsConnectSequence() is run
> before TryRunningQemuKernel().
>
> It reverses commit a34a886962561f6d8550b2a1bb193798ca456431 which aimed
> to improve UEFI boot time. Unfortunately that commit now results in boot
> failure when using qemu's -kernel option, therefore rendering the -initrd
> & -append options useless.
>
> Such failures are seen in all releases from edk2-stable201808 to
> edk2-stable202105 as well as the master branch.
>
Can we pinpoint the failure condition a bit more? I heavily rely on
-kernel for my local OVMF testing and other uses, and I am pretty sure
it hasn't been broken for 3 years.
So what else are you doing that triggers this failure? Is it related
to boot order, the type of devices, etc?
> The last releases which actually work correctly are vUDK2017 and vUDK2018
> as they don't contain the a34a88 commit.
>
> This change has been tested with edk2-stable201808, edk2-stable201811,
> edk2-stable202105 as well as master (at 21/7/2021). It results in correct
> booting using the -kernel option in all the test cases. No measurable
> change in boot times was discernible compared with the unaffected vUDK2017
> & vUDK2018 releases.
>
> Signed-off-by: Christoph Willing <chris.willing@linux.com>
> ---
> OvmfPkg/Library/PlatformBootManagerLib/BdsPlatform.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/OvmfPkg/Library/PlatformBootManagerLib/BdsPlatform.c b/OvmfPkg/Library/PlatformBootManagerLib/BdsPlatform.c
> index b0e9742937..f08ace87b3 100644
> --- a/OvmfPkg/Library/PlatformBootManagerLib/BdsPlatform.c
> +++ b/OvmfPkg/Library/PlatformBootManagerLib/BdsPlatform.c
> @@ -1517,14 +1517,14 @@ PlatformBootManagerAfterConsole (
> Tcg2PhysicalPresenceLibProcessRequest (NULL);
>
> //
> - // Process QEMU's -kernel command line option
> + // Perform some platform specific connect sequence
> //
> - TryRunningQemuKernel ();
> + PlatformBdsConnectSequence ();
>
> //
> - // Perform some platform specific connect sequence
> + // Process QEMU's -kernel command line option
> //
> - PlatformBdsConnectSequence ();
> + TryRunningQemuKernel ();
>
> EfiBootManagerRefreshAllBootOption ();
>
> --
> 2.32.0
>
>
>
> ------------
> Groups.io Links: You receive all messages sent to this group.
> View/Reply Online (#78261): https://edk2.groups.io/g/devel/message/78261
> Mute This Topic: https://groups.io/mt/84497355/5717338
> Group Owner: devel+owner@edk2.groups.io
> Unsubscribe: https://edk2.groups.io/g/devel/unsub [ardb+tianocore@kernel.org]
> ------------
>
>
next prev parent reply other threads:[~2021-08-09 13:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 2:02 [PATCH 0/1] OvmfPkg PlatformBootManagerLib: Move TryRunningQemuKernel() Christoph Willing
2021-07-28 2:02 ` [PATCH 1/1] " Christoph Willing
2021-08-09 13:08 ` Ard Biesheuvel [this message]
[not found] ` <1695D2E15A92C8E7.3876@groups.io>
2021-08-09 12:53 ` [edk2-devel] " Christoph Willing
2021-08-09 14:52 ` James Bottomley
2021-08-10 0:10 ` Christoph Willing
2021-08-10 6:01 ` Gerd Hoffmann
2021-08-10 12:10 ` Christoph Willing
2021-08-10 14:26 ` James Bottomley
2021-08-10 23:04 ` Christoph Willing
2021-08-10 23:24 ` James Bottomley
2021-08-11 0:34 ` Christoph Willing
2021-08-11 6:12 ` Gerd Hoffmann
2021-08-11 9:55 ` Christoph Willing
2021-08-11 10:30 ` Ard Biesheuvel
2021-08-12 12:41 ` Christoph Willing
2021-08-12 13:36 ` Gerd Hoffmann
2021-08-12 14:07 ` Christoph Willing
2021-08-11 6:08 ` Gerd Hoffmann
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-list 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='CAMj1kXHT61zi=eDsObZZaEV7A0g1B3YEkZ6DVjRouvqDN=_bEA@mail.gmail.com' \
--to=devel@edk2.groups.io \
/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