-
Notifications
You must be signed in to change notification settings - Fork 102
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
io: make Read/WriteVolatile implementations optional #311
Conversation
27107fd
to
02f9574
Compare
995c720
to
d39af30
Compare
Btw Paolo, while I got your attention here in rust-vmm land, any chance you have a second to look at #307? :o |
@bonzini can you check tests when only I had something like that (with
This reminds me that we should work on rust-vmm/rust-vmm-ci#152 |
b08e497
to
a132296
Compare
All combinations (tested with |
Thanks for checking! |
@bonzini I think there is another failure in some examples which are tested only when running the tests (so maybe you already discovered running the all tests, but I'm reporting in any case):
|
Signed-off-by: Paolo Bonzini <[email protected]>
I forgot to push that one, sorry. |
a132296
to
4370e3b
Compare
Summary of the PR
Some projects may not want I/O to go directly to libc, for example to avoid any kind of blocking I/O. Make the file descriptor implementations of ReadVolatile and WriteVolatile optional.
The PR is on top of #310.
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).
unsafe
code is properly documented.