-
Notifications
You must be signed in to change notification settings - Fork 114
Rename GuestMemory->GuestMemoryBackend, IoMemory->GuestMemory #362
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
a97d0e1 to
569b637
Compare
|
I'm not sure if this should be 0.18.0 or 0.19.0. @XanClic, I think the current |
|
Thanks! 🙂 |
|
Do you want to keep |
Rename GuestMemory to GuestMemoryBackend, IoMemory to GuestMemory. This allows users of vm-memory to be aware of access permissions for memory, with no change to callers that just use the `Bytes` interface. Signed-off-by: Paolo Bonzini <[email protected]>
569b637 to
c3243a5
Compare
Also rename IoMemorySliceIterator to GuestMemorySliceIterator, and GuestMemorySliceIterator to GusetMemoryBackendSliceIterator. Signed-off-by: Paolo Bonzini <[email protected]>
Signed-off-by: Paolo Bonzini <[email protected]>
After the rename, the primary interface to vm-memory is almost completely absent in DESIGN.md. Give it more importance and remove some details of GuestMemoryBackend that are now obsolete. Signed-off-by: Paolo Bonzini <[email protected]>
Signed-off-by: Paolo Bonzini <[email protected]>
c3243a5 to
c8adfa8
Compare
Summary of the PR
As discussed in #327, make the main interface to vm-memory the one that includes permissions and lets fewer aspects of the implementation through.
Based on #361.
Requirements
Before submitting your PR, please make sure you addressed the following
requirements:
git commit -s), and the commit message has max 60 characters for thesummary and max 75 characters for each description line.
test.
Release" section of CHANGELOG.md (if no such section exists, please create one).
unsafecode is properly documented.