From: "Pedro Falcato" <pedro.falcato@gmail.com>
To: devel@edk2.groups.io, taylor.d.beebe@gmail.com
Cc: "Abner Chang" <abner.chang@amd.com>,
"Andrei Warkentin" <andrei.warkentin@intel.com>,
"Anatol Belski" <anbelski@linux.microsoft.com>,
"Andrew Fish" <afish@apple.com>,
"Anthony Perard" <anthony.perard@citrix.com>,
"Ard Biesheuvel" <ardb+tianocore@kernel.org>,
"Corvin Köhne" <corvink@freebsd.org>,
"Dandan Bi" <dandan.bi@intel.com>,
"Eric Dong" <eric.dong@intel.com>,
"Erdem Aktas" <erdemaktas@google.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Guo Dong" <guo.dong@intel.com>, "Gua Guo" <gua.guo@intel.com>,
"James Bottomley" <jejb@linux.ibm.com>,
"James Lu" <james.lu@intel.com>,
"Jian J Wang" <jian.j.wang@intel.com>,
"Jianyong Wu" <jianyong.wu@arm.com>,
"Jiewen Yao" <jiewen.yao@intel.com>,
"Jordan Justen" <jordan.l.justen@intel.com>,
"Julien Grall" <julien@xen.org>,
"Leif Lindholm" <quic_llindhol@quicinc.com>,
"Liming Gao" <gaoliming@byosoft.com.cn>,
"Michael Roth" <michael.roth@amd.com>,
"Min Xu" <min.m.xu@intel.com>,
"Peter Grehan" <grehan@freebsd.org>,
"Rahul Kumar" <rahul1.kumar@intel.com>,
"Ray Ni" <ray.ni@intel.com>, "Rebecca Cran" <rebecca@bsdio.com>,
"Sami Mujawar" <sami.mujawar@arm.com>,
"Sean Rhodes" <sean@starlabs.systems>,
"Sunil V L" <sunilvl@ventanamicro.com>,
"Tom Lendacky" <thomas.lendacky@amd.com>
Subject: Re: [edk2-devel] [PATCH v2 00/25] Implement Dynamic Memory Protections
Date: Sat, 19 Aug 2023 23:13:26 +0100 [thread overview]
Message-ID: <CAKbZUD0s_Sw1o4WWKurP-_C-16+b0E_uvh0+gvKxU39K-ih5ZA@mail.gmail.com> (raw)
In-Reply-To: <20230818223159.1073-1-taylor.d.beebe@gmail.com>
On Fri, Aug 18, 2023 at 11:57 PM Taylor Beebe <taylor.d.beebe@gmail.com> wrote:
>
> In the past, memory protection settings were configured via FixedAtBuild PCDs,
> which resulted in a build-time configuration of memory mitigations. This
> approach limited the flexibility of applying mitigations to the
> system and made it difficult to update or adjust the settings post-build.
>
> In a design, the configuration interface has been revised to allow for dynamic
> configuration. This is achieved by setting memory protections via a library
> interface which stores/updates the memory protection settings in
> a GUIDed HOB, which is then consumed during and after DXE handoff.
>
> This patch series adds two libraries:
> SetMemoryProtectionsLib: A PEIM that allows for setting/fetching memory
> protections and "locking" to prevent further updates via the library interface.
> The backing for the settings are a GUIDed HOB that is created by the library
> whenever its API is invoked.
>
> GetMemoryProtectionsLib: A DXE library that allows for getting the memory
> protection settings for the current boot. This library populates a global
> with the settings from the HOB entry (if present) for access in the module.
> Previous references to the PCDs are replaced with references to the global.
>
> OvmfPkg has been updated to allow the setting of the memory protection profile
> via QemuCfg instead of just the NxForStack setting. If no profile is passed,
> the platform will default to the Debug profile for DXE and Off profile for MM.
>
> ArmVirtPkg will use the Release profile.
>
> Reference: https://github.com/tianocore/edk2/pull/4566
Hi Taylor,
Would you mind stating what changed between v1 and v2? It would help
reviewing :)
--
Pedro
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#107896): https://edk2.groups.io/g/devel/message/107896
Mute This Topic: https://groups.io/mt/100830898/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2023-08-19 22:13 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 22:31 [edk2-devel] [PATCH v2 00/25] Implement Dynamic Memory Protections Taylor Beebe
2023-08-18 22:31 ` [edk2-devel] [PATCH v2 01/25] MdeModulePkg: Add DXE and MM Memory Protection Settings Definitions Taylor Beebe
2023-08-18 22:31 ` [edk2-devel] [PATCH v2 02/25] MdeModulePkg: Define SetMemoryProtectionsLib and GetMemoryProtectionsLib Taylor Beebe
2023-08-18 22:31 ` [edk2-devel] [PATCH v2 03/25] MdeModulePkg: Add NULL Instances for Get/SetMemoryProtectionsLib Taylor Beebe
2023-08-18 22:31 ` [edk2-devel] [PATCH v2 04/25] MdeModulePkg: Implement SetMemoryProtectionsLib and GetMemoryProtectionsLib Taylor Beebe
2023-08-18 22:31 ` [edk2-devel] [PATCH v2 05/25] MdeModulePkg: Apply Protections to the HOB List Taylor Beebe
2023-08-18 22:31 ` [edk2-devel] [PATCH v2 06/25] MdeModulePkg: Check Print Level Before Dumping GCD Memory Map Taylor Beebe
2023-08-18 22:31 ` [edk2-devel] [PATCH v2 07/25] UefiCpuPkg: Always Set Stack Guard in MpPei Init Taylor Beebe
2023-08-18 22:31 ` [edk2-devel] [PATCH v2 08/25] ArmVirtPkg: Add Memory Protection Library Definitions to Platforms Taylor Beebe
2023-08-18 22:31 ` [edk2-devel] [PATCH v2 09/25] OvmfPkg: " Taylor Beebe
2023-08-18 22:31 ` [edk2-devel] [PATCH v2 10/25] OvmfPkg: Apply Memory Protections via SetMemoryProtectionsLib Taylor Beebe
2023-08-18 22:31 ` [edk2-devel] [PATCH v2 11/25] OvmfPkg: Update PeilessStartupLib to use SetMemoryProtectionsLib Taylor Beebe
2023-08-18 22:31 ` [edk2-devel] [PATCH v2 12/25] UefiPayloadPkg: Update DXE Handoff " Taylor Beebe
2023-08-18 22:31 ` [edk2-devel] [PATCH v2 13/25] MdeModulePkg: " Taylor Beebe
2023-08-18 22:31 ` [edk2-devel] [PATCH v2 14/25] ArmPkg: Use GetMemoryProtectionsLib instead of Memory Protection PCDs Taylor Beebe
2023-08-18 22:31 ` [edk2-devel] [PATCH v2 15/25] EmulatorPkg: " Taylor Beebe
2023-08-18 22:31 ` [edk2-devel] [PATCH v2 16/25] OvmfPkg: " Taylor Beebe
2023-08-18 22:31 ` [edk2-devel] [PATCH v2 17/25] UefiCpuPkg: " Taylor Beebe
2023-08-18 22:31 ` [edk2-devel] [PATCH v2 18/25] MdeModulePkg: " Taylor Beebe
2023-08-18 22:31 ` [edk2-devel] [PATCH v2 19/25] MdeModulePkg: Add Additional Profiles to SetMemoryProtectionsLib Taylor Beebe
2023-08-29 10:46 ` Gerd Hoffmann
2023-08-29 16:08 ` Taylor Beebe
2023-08-18 22:31 ` [edk2-devel] [PATCH v2 20/25] OvmfPkg: Enable Choosing Memory Protection Profile via QemuCfg Taylor Beebe
2023-08-29 11:17 ` Gerd Hoffmann
2023-08-29 16:26 ` Taylor Beebe
2023-08-18 22:31 ` [edk2-devel] [PATCH v2 21/25] ArmVirtPkg: Apply Memory Protections via SetMemoryProtectionsLib Taylor Beebe
2023-08-18 22:31 ` [edk2-devel] [PATCH v2 22/25] MdeModulePkg: Delete PCD Profile from SetMemoryProtectionsLib Taylor Beebe
2023-08-18 22:31 ` [edk2-devel] [PATCH v2 23/25] OvmfPkg: Delete Memory Protection PCDs Taylor Beebe
2023-08-18 22:31 ` [edk2-devel] [PATCH v2 24/25] ArmVirtPkg: " Taylor Beebe
2023-08-18 22:31 ` [edk2-devel] [PATCH v2 25/25] MdeModulePkg: " Taylor Beebe
2023-08-19 22:13 ` Pedro Falcato [this message]
2023-08-21 16:19 ` [edk2-devel] [PATCH v2 00/25] Implement Dynamic Memory Protections Taylor Beebe
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=CAKbZUD0s_Sw1o4WWKurP-_C-16+b0E_uvh0+gvKxU39K-ih5ZA@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