Tests/chihiro stuffs #1806
Draft
Tests/chihiro stuffs #1806
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
GXTX
force-pushed
the
tests/chihiro_stuffs
branch
2 times, most recently
from
39b0ce9 to
cb0145d
Compare
GXTX
force-pushed
the
tests/chihiro_stuffs
branch
from
986d4a9 to
47510f0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Just doing some quick bring-ups of old stuff.
Maybe an interested party can continue and actually hookup the block driver to a device. :)
The
DriveInfostruct changed at some point and doesn't allow specifying it'sBlockDriverBlockDriver's themselves also changed and no longer accept member functionsRather, are expecting some AIO, or CO? functions,
bdrv_co_preadv,bdrv_aoi_preadv.I didn't dig into what the difference between the 2 are and just hooked up the memory_read/write functions do the CO type.