update vm-memory version #4
Conversation
|
|
|
@liubogithub vm-memory moved to 0.4.0 a few days ago. I think we should move both fuse-backend and this crate to that release. |
The vm-memory 0.4 version has fixed a performance regression issue:) |
A pretty big one, yes :) |
|
OK, I will update both accordingly. |
vm-memory 0.3.0+ has removed integer-atomics as distinct feature. Sameo suggested vm-memory 0.4.0 as it has fixed a performance issue. Signed-off-by: Liu Bo <[email protected]>
|
Please also pay attention to that, there's no methods to access guest memory atomically. If there are concurrently accesses to the same fields from guest and vmm side, we need to use atomic access interfaces. |
vm-memory 0.3.0 has removed integer-atomics as distinct feature.
Signed-off-by: Liu Bo [email protected]