From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, ard.biesheuvel@linaro.org,
Sami Mujawar <sami.mujawar@arm.com>
Cc: Leif Lindholm <leif.lindholm@linaro.org>,
Matteo Carlini <Matteo.Carlini@arm.com>, nd <nd@arm.com>
Subject: Re: [edk2-devel] [PATCH v1 1/1] ArmPkg: Dispatch deferred images after EndOfDxe
Date: Fri, 6 Dec 2019 01:07:44 +0100 [thread overview]
Message-ID: <9889532a-d188-e784-3b00-22631bcdc625@redhat.com> (raw)
In-Reply-To: <2689eabf-b2a4-466b-d0cc-f8786e7a35ee@redhat.com>
On 12/06/19 00:54, Laszlo Ersek wrote:
> The proper solution would be the following (if I may suggest an idea):
>
> (1) fix ArmVirtPkg: hoist the following part:
>
>> //
>> // Locate the PCI root bridges and make the PCI bus driver connect each,
>> // non-recursively. This will produce a number of child handles with PciIo on
>> // them.
>> //
>> FilterAndProcess (&gEfiPciRootBridgeIoProtocolGuid, NULL, Connect);
>>
>> //
>> // Signal the ACPI platform driver that it can download QEMU ACPI tables.
>> //
>> EfiEventGroupSignal (&gRootBridgesConnectedEventGroupGuid);
>
> above this part:
>
>> //
>> // Signal EndOfDxe PI Event
>> //
>> EfiEventGroupSignal (&gEfiEndOfDxeEventGroupGuid);
>>
>> //
>> // Dispatch deferred images after EndOfDxe event.
>> //
>> EfiBootManagerDispatchDeferredImages ();
>
> This will make:
>
> - ArmVirtPkg match the order employed in OvmfPkg,
>
> - EfiBootManagerDispatchDeferredImages() pick up PCI option ROMs,
>
> - run the ACPI platform driver *before* EndOfDxe; but that's just fine.
> (In fact, in OvmfPkg, that's *required*. See the FACS note there.)
>
>
> (2) Port the same fix to ArmPkg: namely move
>
>> //
>> // Locate the PCI root bridges and make the PCI bus driver connect each,
>> // non-recursively. This will produce a number of child handles with PciIo on
>> // them.
>> //
>> FilterAndProcess (&gEfiPciRootBridgeIoProtocolGuid, NULL, Connect);
>
> just above
>
>> //
>> // Signal EndOfDxe PI Event
>> //
>> EfiEventGroupSignal (&gEfiEndOfDxeEventGroupGuid);
>
>
> (3) In a separate patch, call EfiBootManagerDispatchDeferredImages()
> just after the *new* location of signaling EndOfDxe.
So given that commit 0f9395d7c5cc6ae2beaa2d87008fe158d04a8069 exists
now, I think we should do (1), and then port it whole-sale to ArmPkg.
... Unless of course my analysis is wrong. :)
Thanks
Laszlo
prev parent reply other threads:[~2019-12-06 0:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 14:01 [PATCH v1 1/1] ArmPkg: Dispatch deferred images after EndOfDxe Sami Mujawar
2019-05-02 8:14 ` Ard Biesheuvel
2019-12-05 20:25 ` Ard Biesheuvel
2019-12-05 23:54 ` [edk2-devel] " Laszlo Ersek
2019-12-06 0:04 ` Laszlo Ersek
2019-12-06 10:02 ` Ard Biesheuvel
2019-12-06 10:33 ` Laszlo Ersek
2019-12-06 11:01 ` Ard Biesheuvel
2019-12-06 0:07 ` Laszlo Ersek [this message]
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=9889532a-d188-e784-3b00-22631bcdc625@redhat.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