Memory Map Semantics
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 155
- Forks
- 42
- Avg merge
- 23h 53m
- Merged PRs (30d)
- 3
Description
https://github.com/microsoft/igvm/blob/main/igvm_defs/src/lib.rs#L1160-L1217
Can you help me understand the motivations behind defining a custom memory map for IGVM?
I've tried to divine the reasons for this. Compared to e820, you've just added 3 flags (purpose, vtl2 and hidden) and compared to EFI_MEMORY_DESCRIPTOR you've removed a bunch of flags and added 2 flags (vtl2 and hidden). Both vtl2 and hidden are also listed as unstable.
Is there a reason not to just use/extend e820 or EFI_MEMORY_DESCRIPTOR?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with igvm_defs/src/lib.rs lines 1160-1217 and compare the custom memory-map fields with e820 and EFI_MEMORY_DESCRIPTOR, as described in the issue. Determine the intended rationale for the additional and removed flags, then document the decision and the status of the unstable fields if maintainers confirm it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100