igvm_defs: indicate that it is legal for a pagetable region to lie within a relocation region
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 155
- Forks
- 42
- Avg merge
- 23h 53m
- Merged PRs (30d)
- 3
Description
The spec today does not allow this, but some of our loader implementations allow this. The reason being:
- It's important to allow marking a larger region as relocatable, as some headers may describe the larger region as relocatable, say for required memory.
- We want to describe that pagetables should be relocated with another region, and relocated the same as that outer region.
The update here is to change the description for IGVM_VHS_PAGE_TABLE_RELOCATION to allow it to lie within another relocation region, and indicate that it must be relocated with the outer region it's included in.
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 the IGVM_VHS_PAGE_TABLE_RELOCATION definition and its documentation in igvm_defs, as referenced by the docs.rs link. Update the description to permit nesting within another relocation region and state that the page-table region follows the outer region's relocation; confirm the resulting documentation matches the issue's two requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100