Memory Protections: Configuration Interface

tianocore / projects

Empty repository to track all issues associated with TianoCore Projects

1 stars 0 forks source link

Memory Protections: Configuration Interface #1

Open makubacki opened 1 year ago

makubacki commented 1 year ago

This issue tracks work related to defining a stable memory protection configuration interface.

### Configuration tasks
- [ ] https://github.com/tianocore/projects/issues/13
- [ ] https://github.com/tianocore/projects/issues/12
- [ ] https://github.com/tianocore/projects/issues/11
- [ ] https://github.com/tianocore/projects/issues/8
- [ ] https://github.com/tianocore/projects/issues/10
- [ ] https://github.com/tianocore/projects/issues/9

niruiyu commented 1 year ago

What's the diff between minimal tianocore/projects#8 and default settings tianocore/projects#10? Is that something like: "EDKII protection capability" >= "Default" >= "Minimal"

niruiyu commented 1 year ago

There are lots of tasks. Hard for me to understand what big goals we are targeting. Better to have a tree layout that clearly explains their relationships. The roots of trees can help people understand each "big goal".

makubacki commented 1 year ago

What's the diff between minimal tianocore/projects#8 and default settings tianocore/projects#10? Is that something like: "EDKII protection capability" >= "Default" >= "Minimal"

tianocore/projects#8
- Realistically, we expect that not every platform in the world is going to be able to adopt the most stringent level of memory protections that can be implemented. A "minimally" protected system is the technical description of what is considered minimum protection and why. This is what every system is expected to adopt.
tianocore/projects#10
- This is less verbose and simply translates the human description of a minimally protected system in 4494 into the actual settings that will be used in the code to realize it.

So, the idea is that "Minimally Protected System" == "Default".

makubacki commented 1 year ago

There are lots of tasks. Hard for me to understand what big goals we are targeting. Better to have a tree layout that clearly explains their relationships. The roots of trees can help people understand each "big goal".

Hopefully the meeting yesterday helped explain the relationships. The tasks are organized under GitHub Tasklists.

Here's a quick way to check if a task is tracked by another task or not (download or click the image to see it larger.).

I also talked about this in this week's Tianocore Tools & CI meeting. When that recording is published to YouTube, I'll add link here.