[RFC] Rust supervisor proposal

[kuqin12]

Description

This proposal intends to provide a supervised Standalone MM solution with Rust.

• Impacts functionality?
• Impacts security?
• Breaking change?
• Includes tests?
• Includes documentation?

How This Was Tested

RFC only.

Integration Instructions

N/A

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[joschock]

General feedback: since this is a Patina RFC, I think it would be good to have a section that helps to better understand how this RFC would impact and connect with existing Patina code. For example, here are some questions I think you could answer to clarify the Patina/MM relationship:

1. Will the MM core be a separate repo? Or do you plan to build an MM core lib crate in parallel with patina_dxe_core?
2. How do you anticipate the MM consuming patina modules (like allocator/events/protocol_db)? Or do you plan to use patina modules as reference and just fork new separate MM implementations?
3. Are there any significant architectural changes required to existing patina need to accommodate/enable the MM design?

[kuqin12]

General feedback: since this is a Patina RFC, I think it would be good to have a section that helps to better understand how this RFC would impact and connect with existing Patina code. For example, here are some questions I think you could answer to clarify the Patina/MM relationship:

1. Will the MM core be a separate repo? Or do you plan to build an MM core lib crate in parallel with patina_dxe_core?
2. How do you anticipate the MM consuming patina modules (like allocator/events/protocol_db)? Or do you plan to use patina modules as reference and just fork new separate MM implementations?
3. Are there any significant architectural changes required to existing patina need to accommodate/enable the MM design?

Thanks, I updated the RFC to include 2 nutrient content tables to reflect such. But the short summary is that I would like to make the new supevisor sitting in parallel with dxe_core amd move some common functional modules out from patina_core_dxe so that they can be shared.

Then for the newly authored code, such as syscall dispatcher and privilege manager, I intend to produce them as their own crate. What if we want to use them in DXE core one day..? 😈

[patina-automation]

QEMU Validation Failed

QEMU validation did not complete successfully or did not shutdown as expected.

Workflow run: https://github.com/OpenDevicePartnership/patina/actions/runs/23207006610

Job Results

Job	Result
Gather Incoming PR Metadata	✅
Run Patina QEMU Validation / Preflight Checks	✅
Run Patina QEMU Validation / Post In-Progress Notification	✅
Run Patina QEMU Validation / Get Constants / Get Repository Constants	✅
Run Patina QEMU Validation / Validate QEMU Q35 (Windows)	✅
Run Patina QEMU Validation / Validate QEMU - Q35 (Linux)	❌
Run Patina QEMU Validation / Validate QEMU - SBSA (Linux)	❌
Run Patina QEMU Validation / Emit PR Metadata	✅

This comment was automatically generated by the Patina QEMU PR Validation Post workflow.