On Thu, Aug 07, 2025 at 08:30:01PM +0800, Zhao Liu wrote:
> Date: Thu, 7 Aug 2025 20:30:01 +0800
> From: Zhao Liu <zhao1....@intel.com>
> Subject: [RFC 00/26] rust/memory: Integrate the vm-memory API from rust-vmm
> X-Mailer: git-send-email 2.34.1
>
> Hi,
>
> This RFC series explores integrating the vm-memory API into QEMU's
> rust/memory bindings.
>
> Thanks to Paolo and Manos's many suggestions and feedback, I have
> resolved many issues over the past few months, but there are still
> some open issues that I would like to discuss.
>
> This series finally provides the following safe interfaces in Rust:
> * AddressSpace::write in Rust <=> address_space_write in C
> - **but only** supports MEMTXATTRS_UNSPECIFIED
>
> * AddressSpace::read in Rust <=> address_space_read_full in C
> - **but only** supports MEMTXATTRS_UNSPECIFIED.
>
> * AddressSpace::store in Rust <=> address_space_st{size} in C
> - **but only** supports MEMTXATTRS_UNSPECIFIED and native endian.
>
> * AddressSpace::load in Rust <=> address_space_ld{size} in C
> - **but only** supports MEMTXATTRS_UNSPECIFIED and native endian.
>
> And this series involves changes mainly to these three parts:
> * NEW QEMU memory APIs wrapper at C side.
> * Extra changes for vm-memory (downstream for now).
> * NEW QEMU memory bindings/APIs based on vm-memory at Rust side.
>
> Although the number of line changes appears to be significant, more
> than half of them are documentation and comments.
>
> (Note: the latest vm-memory v0.16.2 crate didn't contain Paolo's
> commit 5f59e29c3d30 ("guest_memory: let multiple regions slice one
> global bitmap"), so I have to pull the vm-memory from github directly.)
>
> Thanks for your feedback!
BTW, this is my branch which includes all the patches:
https://gitlab.com/zhao.liu/qemu/-/tree/rust-vm-memory-v1-08-04-2025
Regards,
Zhao
