Separate VA reservation from mapping/allocation on Windows
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.7k
- Forks
- 144
- Avg merge
- 12h 21m
- Merged PRs (30d)
- 146
Description
I don't think it's a problem--those reserved VAs are owned by us.
There are other problems, though, because even while we're looping over the mappings, the mappings could change. I think ultimately we need to change Windows to use placeholders --this will allow us to separate VA reservation from mapping/allocation.
_Originally posted by @jstarks in https://github.com/microsoft/litebox/pull/488#discussion_r2520772316_
Contributor guide
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 by reading the Windows mapping/allocation loop discussed in the issue and the linked Windows placeholder documentation. Determine how VA reservation can be separated from mapping and allocation, and verify that mappings cannot change unexpectedly during iteration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100