From: Akihiko Odaki <akihiko.odaki@gmail.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Ani Sinha" <anisinha@redhat.com>,
"Igor Mammedov" <imammedo@redhat.com>
Subject: Re: [PULL 0/8] Firmware/edk2 20230918 patches
Date: Sat, 18 Nov 2023 01:00:58 +0900 [thread overview]
Message-ID: <5edb0f5c-6070-411a-b9f5-b05275ddc708@gmail.com> (raw)
In-Reply-To: <jn7jj2lcb5qab7kpi3x46xhli257h7wqyk5ioe74a3etjdl4ga@uz3imwwenks6>
On 2023/11/13 20:09, Gerd Hoffmann wrote:
>> Hi,
>>
>> This apparently broke EDK2 for AArch64. I tried the following command:
>> build/qemu-system-aarch64 -drive
>> file=build/pc-bios/edk2-aarch64-code.fd,format=raw,if=pflash,readonly=on -M
>> virt -cpu max -nographic -cdrom Fedora-Silverblue-ostree-aarch64-37-1.7.iso
>
> https://bugzilla.redhat.com/show_bug.cgi?id=2113005
>
> tl:dr: shim is broken, and recent edk2 starting to expose
> EFI_MEMORY_ATTRIBUTE_PROTOCOL makes the bug visible (without
> the protocol the buggy code path is never taken).
>
> take care,
> Gerd
>
That's unfortunate. Thanks for the info.
Regards,
Akihiko Odaki
prev parent reply other threads:[~2023-11-17 16:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 13:33 [PULL 0/8] Firmware/edk2 20230918 patches Gerd Hoffmann
2023-09-18 13:33 ` [PULL 1/8] tests/acpi: allow virt/SSDT.memhp updates Gerd Hoffmann
2023-09-18 13:33 ` [PULL 2/8] edk2: update build script Gerd Hoffmann
2023-09-18 13:33 ` [PULL 3/8] edk2: update build config Gerd Hoffmann
2023-09-18 13:33 ` [PULL 4/8] edk2: workaround edk-stable202308 bug Gerd Hoffmann
2023-09-18 13:33 ` [PULL 5/8] edk2: update submodule to edk2-stable202308 Gerd Hoffmann
2023-09-18 13:33 ` [PULL 7/8] tests/acpi: update virt/SSDT.memhp Gerd Hoffmann
2023-09-18 13:33 ` [PULL 8/8] tests/acpi: disallow virt/SSDT.memhp updates Gerd Hoffmann
2023-09-19 19:13 ` [PULL 0/8] Firmware/edk2 20230918 patches Stefan Hajnoczi
2023-11-11 17:19 ` Akihiko Odaki
2023-11-13 11:09 ` Gerd Hoffmann
2023-11-17 16:00 ` Akihiko Odaki [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-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=5edb0f5c-6070-411a-b9f5-b05275ddc708@gmail.com \
--to=akihiko.odaki@gmail.com \
--cc=anisinha@redhat.com \
--cc=imammedo@redhat.com \
--cc=kraxel@redhat.com \
--cc=mst@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.