Skip to content

update vm-memory version#4

Open
liubogithub wants to merge 1 commit intocloud-hypervisor:dragonballfrom
liubogithub:deps
Open

update vm-memory version#4
liubogithub wants to merge 1 commit intocloud-hypervisor:dragonballfrom
liubogithub:deps

Conversation

@liubogithub
Copy link
Copy Markdown

@liubogithub liubogithub commented Oct 22, 2020

vm-memory 0.3.0 has removed integer-atomics as distinct feature.

Signed-off-by: Liu Bo bo.liu@linux.alibaba.com

@liubogithub
Copy link
Copy Markdown
Author

liubogithub commented Oct 22, 2020

fuse-backend-rs fails to build because of vm-memory version conflict.

@liubogithub
Copy link
Copy Markdown
Author

liubogithub commented Nov 25, 2020 •
edited
Loading

@sameo Hi, could you please help merge this commit? it's required by this fuse-backend-rs pr

cloud-hypervisor/fuse-backend-rs#10

@liubogithub liubogithub mentioned this pull request Nov 25, 2020
Closed
@sameo
Copy link
Copy Markdown
Member

sameo commented Nov 25, 2020

@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.

@jiangliu
Copy link
Copy Markdown

jiangliu commented Nov 25, 2020

@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:)

@sameo
Copy link
Copy Markdown
Member

sameo commented Nov 25, 2020

@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 :)

@liubogithub
Copy link
Copy Markdown
Author

liubogithub commented Nov 25, 2020

OK, I will update both accordingly.

@liubogithub
Update vm-memory
b92870d 
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 <bo.liu@linux.alibaba.com>
@jiangliu
Copy link
Copy Markdown

jiangliu commented Nov 26, 2020

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

1 more reviewer

@jiangliu jiangliu jiangliu approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@liubogithub @sameo @jiangliu