From: "Gerd Hoffmann" <kraxel@redhat.com>
To: Oliver Steffen <osteffen@redhat.com>
Cc: devel@edk2.groups.io, Ard Biesheuvel <ardb+tianocore@kernel.org>,
Daniel Schaefer <git@danielschaefer.me>,
Eric Dong <eric.dong@intel.com>,
Leif Lindholm <quic_llindhol@quicinc.com>,
Liming Gao <gaoliming@byosoft.com.cn>,
Michael D Kinney <michael.d.kinney@intel.com>,
Rahul Kumar <rahul1.kumar@intel.com>, Ray Ni <ray.ni@intel.com>,
Sami Mujawar <sami.mujawar@arm.com>,
Sunil V L <sunilvl@ventanamicro.com>,
Zhiguang Liu <zhiguang.liu@intel.com>
Subject: Re: [PATCH 1/1] ArmPkg: Add Pcd to disable EFI_MEMORY_ATTRIBUTE_PROTOCOL
Date: Tue, 20 Jun 2023 11:32:55 +0200 [thread overview]
Message-ID: <rkq7clawcm537wzel4s3rcfas7zxycjlgsbdd4pw6sohj5qjlh@c54vs6opt55h> (raw)
In-Reply-To: <20230619203244.228933-1-osteffen@redhat.com>
On Mon, Jun 19, 2023 at 10:32:25PM +0200, Oliver Steffen wrote:
> Recent versions of shim (15.6 and 15.7) crash when the newly added
> EFI_MEMORY_ATTRIBUTE_PROTOCOL is provided by the firmware. To allow
> existing installations to boot, provide a workaround in form of a Pcd
> that allows tuning it off at build time (defaults to 'enabled').
Background: We have untested + broken code for
EFI_MEMORY_ATTRIBUTE_PROTOCOL support in the listed shim releases.
Now that firmware starts to actually provide that protocol the
time bomb explodes.
> --- a/ArmPkg/ArmPkg.dec
> +++ b/ArmPkg/ArmPkg.dec
> @@ -172,6 +172,9 @@ [PcdsFixedAtBuild.common]
> gArmTokenSpaceGuid.PcdCpuVectorBaseAddress|0xffff0000|UINT64|0x00000004
> gArmTokenSpaceGuid.PcdCpuResetAddress|0x00000000|UINT32|0x00000005
>
> + # Enable/Disable EFI_MEMORY_ATTRIBUTE_PROTOCOL
> + gArmTokenSpaceGuid.PcdEnableEfiMemoryAttributeProtocol|TRUE|BOOLEAN|0x000000EE
> +
> #
> # ARM Secure Firmware PCDs
> #
Given that I expect we will run into the very same problem on x64 as
soon as EFI_MEMORY_ATTRIBUTE_PROTOCOL gets enabled there we should
probably define the PCD in MdePkg not ArmPkg (which implies splitting
the patch into a mini series with one MdePkg and one ArmPkg patch).
take care,
Gerd
next prev parent reply other threads:[~2023-06-20 9:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 20:32 [PATCH 1/1] ArmPkg: Add Pcd to disable EFI_MEMORY_ATTRIBUTE_PROTOCOL Oliver Steffen
2023-06-20 9:32 ` Gerd Hoffmann [this message]
2023-06-20 13:16 ` Ard Biesheuvel
2023-06-20 14:53 ` [edk2-devel] " Michael Kubacki
2023-06-20 16:03 ` Gerd Hoffmann
2023-06-20 17:06 ` [edk2-devel] " Sean
2023-06-23 16:26 ` Ard Biesheuvel
2023-06-23 19:32 ` Sean
2023-10-05 6:31 ` Nhi Pham via groups.io
2023-10-05 8:23 ` Laszlo Ersek
2023-10-05 10:01 ` 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=rkq7clawcm537wzel4s3rcfas7zxycjlgsbdd4pw6sohj5qjlh@c54vs6opt55h \
--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