Intercepting vmbus devices makes VTL2 RAM accessible to VTL0
@chris-oo is already working on this.
Since Feb 18, 2025.
- Dominant language
- Rust
- Stars
- 1.9k
- Forks
- 238
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 100
Description
Make sure we are happy with VtlMemoryProtection::modify_vtl_page_setting and its usage. Alternatives could include setting aside RAM to use for this purpose, changing signature so memory can not be deallocated while not properly protected, always leak memory after this use so it can never be reused, etc.
There's some considerations if we should carve out special regions of the VTL2 GPA ranges so that we cannot use that ram for any other purposes. I think if we know exactly how large this would be, that would be desirable so that we can never have this reuse issue where the we could make pages accessible by VTL0 that VTL2 could later use for something else.
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.
Assessment
This issue has not been assessed yet.