Update to vm-memory 0.13.1

Ablu commented 10 months ago

Mostly this introduces the traits WriteVolatile and ReadVolatile. Since these can deal more efficiently deal with the volatile semantics, some old methods got deprecated.

Mostly that means replacing Read/Write with {Read,Write}Volatile.

Requirements

Before submitting your PR, please make sure you addressed the following requirements:

[x] All commits in this PR are signed (with git commit -s), and the commit message has max 60 characters for the summary and max 75 characters for each description line.
[x] All added/changed functionality has a corresponding unit/integration test.
[x] All added/changed public-facing functionality has entries in the "Upcoming Release" section of CHANGELOG.md (if no such section exists, please create one).
[x] Any newly added unsafe code is properly documented.

epilys commented 10 months ago

@Ablu There are some CI compilation errors, can you check them out?

Ablu commented 10 months ago

@Ablu There are some CI compilation errors, can you check them out?

eh... I built with export RUSTFLAGS="-D warnings"! Will check out what goes wrong...

EDIT: Ah, missed --all-features

Ablu commented 10 months ago

fixed (hopefully).

stefano-garzarella commented 10 months ago

@Ablu looks like we need to update vm-memory also in fuzz/common/Cargo.toml

Ablu commented 10 months ago

Looks like aarch64 fails building since it now has two versions of vm-memory in the dependency tree:

Compiling vm-memory v0.13.1
Compiling vm-memory v0.12.2

Investigating...

Ablu commented 10 months ago

@Ablu looks like we need to update vm-memory also in fuzz/common/Cargo.toml

yeah, looks like my regex somehow missed that... Fixed now.

Ablu commented 10 months ago

Rebased from Github UI

rust-vmm / vm-virtio

Update to vm-memory 0.13.1 #261

Requirements