From: "Taylor Beebe" <t@taylorbeebe.com>
To: devel@edk2.groups.io
Cc: spbrogan@outlook.com, eric.dong@intel.com, ray.ni@intel.com,
rahul1.kumar@intel.com, mikuback@linux.microsoft.com,
jian.j.wang@intel.com, hao.a.wu@intel.com, dandan.bi@intel.com,
gaoliming@byosoft.com.cn, guo.dong@intel.com,
maurice.ma@intel.com, benjamin.you@intel.com
Subject: Re: [edk2-devel] [RFC] MemoryProtectionLib for Dynamic Memory Guard Settings
Date: Wed, 28 Jul 2021 12:00:34 -0700 [thread overview]
Message-ID: <442367ad-6504-bedf-9aa9-104626beb056@taylorbeebe.com> (raw)
In-Reply-To: <169445B722413ACA.14473@groups.io>
Note: I'll be accepting feedback on this until Friday after which I will
submit a patch series.
On 7/22/2021 5:32 PM, Taylor Beebe via groups.io wrote:
> Current memory protection settings rely on FixedAtBuild PCD values
> (minus PcdSetNxForStack). Because of this, the memory protection
> configuration interface is fixed in nature. Cases arise in which memory
> protections might need to be adjusted between boots (if platform design
> allows) to avoid disabling a system. For example, platforms might choose
> to allow the user to control their protection policies such as allow
> execution of critical 3rd party software that might violate memory
> protections.
>
> This RFC seeks your feedback regarding introducing an interface that
> allows dynamic configuration of memory protection settings.
>
> I would like to propose two options:
> 1. Describing the memory protection setting configuration in a HOB that
> is produced by the platform.
> 2. Introducing a library class (e.g. MemoryProtectionLib) that allows
> abstraction of the memory protection setting configuration data source.
>
> In addition, I would like to know if the memory protection FixedAtBuild
> PCDs currently in MdeModulePkg can be removed so we can move the
> configuration interface entirely to an option above.
>
> In any case, I would like the settings to be visible to environments
> such as Standalone MM where dynamic PCDs are not accessible.
>
> I am seeking your feedback on this proposal in preparation for sending
> an edk2 patch series.
>
--
Taylor Beebe
Software Engineer @ Microsoft
next parent reply other threads:[~2021-07-28 19:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <169445B722413ACA.14473@groups.io>
2021-07-28 19:00 ` Taylor Beebe [this message]
2021-07-23 0:32 [RFC] MemoryProtectionLib for Dynamic Memory Guard Settings t
2021-07-29 2:18 ` Wang, Jian J
2021-07-30 1:54 ` Taylor Beebe
2021-07-30 1:57 ` Yao, Jiewen
2021-07-30 2:06 ` Taylor Beebe
2021-07-30 2:34 ` Yao, Jiewen
2021-07-30 18:42 ` [edk2-devel] " Sean
2021-07-30 22:25 ` Taylor Beebe
2021-07-31 1:38 ` Yao, Jiewen
2021-08-02 2:35 ` Ni, Ray
2021-08-02 19:56 ` Andrew Fish
2021-08-06 22:11 ` Andrew Fish
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=442367ad-6504-bedf-9aa9-104626beb056@taylorbeebe.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