From: Paolo Bonzini <pbonzini@redhat.com>
To: "Zhao Liu" <zhao1.liu@intel.com>, "Peter Xu" <peterx@redhat.com>,
"David Hildenbrand" <david@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Manos Pitsidianakis" <manos.pitsidianakis@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Junjie Mao" <junjie.mao@hotmail.com>
Cc: qemu-devel@nongnu.org, qemu-rust@nongnu.org,
Dapeng Mi <dapeng1.mi@linux.intel.com>,
Chuanxiao Dong <chuanxiao.dong@intel.com>
Subject: Re: [RFC 24/26] rust/memory: Provide AddressSpace bindings
Date: Thu, 7 Aug 2025 15:50:45 +0200 [thread overview]
Message-ID: <3ce35920-919b-4caf-87c5-b92bd603388a@redhat.com> (raw)
In-Reply-To: <20250807123027.2910950-25-zhao1.liu@intel.com>
On 8/7/25 14:30, Zhao Liu wrote:
> +impl GuestAddressSpace for AddressSpace {
> + type M = FlatView;
> + type T = FlatViewRefGuard;
> +
> + /// Get the memory of the [`AddressSpace`].
> + ///
> + /// This function retrieves the [`FlatView`] for the current
> + /// [`AddressSpace`]. And it should be called from an RCU
> + /// critical section. The returned [`FlatView`] is used for
> + /// short-term memory access.
> + ///
> + /// Note, this function method may **panic** if [`FlatView`] is
> + /// being distroying. Fo this case, we should consider to providing
> + /// the more stable binding with [`bindings::address_space_get_flatview`].
> + fn memory(&self) -> Self::T {
> + let flatp = unsafe { address_space_to_flatview(self.0.as_mut_ptr()) };
> + FlatViewRefGuard::new(unsafe { Self::M::from_raw(flatp) }).expect(
> + "Failed to clone FlatViewRefGuard: the FlatView may have been destroyed concurrently.",
> + )
This is essentially address_space_get_flatview(). You can call it
directly, or you need to loop if FlatViewRefGuard finds a zero reference
count.
> + }
> +}
> +
> +impl AddressSpace {
> + /// The write interface of `AddressSpace`.
> + ///
> + /// This function is similar to `address_space_write` in C side.
> + ///
> + /// But it assumes the memory attributes is MEMTXATTRS_UNSPECIFIED.
> + pub fn write(&self, buf: &[u8], addr: GuestAddress) -> Result<usize> {
> + rcu_read_lock();
> + let r = self.memory().deref().write(buf, addr);
> + rcu_read_unlock();
self.memory() must not need rcu_read_lock/unlock around it, they should
be called by the memory() function itself.
> + r.map_err(guest_mem_err_to_qemu_err)
> + }
I think it's ok to return the vm-memory error. Ultimately, the error
will be either ignored or turned into a device error condition, but I
don't think it's ever going to become an Error**.
> + /// The store interface of `AddressSpace`.
> + ///
> + /// This function is similar to `address_space_st{size}` in C side.
> + ///
> + /// But it only assumes @val follows target-endian by default. So ensure
> + /// the endian of `val` aligned with target, before using this method.
QEMU is trying to get rid of target endianness. We should use the
vm-memory BeNN and LeNN as much as possible. It would be great if you
could write either
ADDRESS_SPACE_MEMORY.store::<Le32>(addr, 42);
or
let n = Le32(42);
ADDRESS_SPACE_MEMORY.store(addr, n);
but not
ADDRESS_SPACE_MEMORY.store(addr, 42);
(Also I've not looked at the patches closely enough, but wouldn't
store() use *host* endianness? Same in patch 23).
Paolo
> + /// And it assumes the memory attributes is MEMTXATTRS_UNSPECIFIED.
> + pub fn store<T: AtomicAccess>(&self, addr: GuestAddress, val: T) -> Result<()> {
> + rcu_read_lock();
> + let r = self.memory().deref().store(val, addr, Ordering::Relaxed);
> + rcu_read_unlock();
> + r.map_err(guest_mem_err_to_qemu_err)
> + }
> +
> + /// The load interface of `AddressSpace`.
> + ///
> + /// This function is similar to `address_space_ld{size}` in C side.
> + ///
> + /// But it only support target-endian by default. The returned value is
> + /// with target-endian.
> + ///
> + /// And it assumes the memory attributes is MEMTXATTRS_UNSPECIFIED.
> + pub fn load<T: AtomicAccess>(&self, addr: GuestAddress) -> Result<T> {
> + rcu_read_lock();
> + let r = self.memory().deref().load(addr, Ordering::Relaxed);
> + rcu_read_unlock();
> + r.map_err(guest_mem_err_to_qemu_err)
> + }
> +}
> +
> +/// The safe binding around [`bindings::address_space_memory`].
> +///
> +/// `ADDRESS_SPACE_MEMORY` provides the complete address space
> +/// abstraction for the whole Guest memory.
> +pub static ADDRESS_SPACE_MEMORY: &AddressSpace = unsafe {
> + let ptr: *const bindings::AddressSpace = addr_of!(address_space_memory);
> +
> + // SAFETY: AddressSpace is #[repr(transparent)].
> + let wrapper_ptr: *const AddressSpace = ptr.cast();
> +
> + // SAFETY: `address_space_memory` structure is valid in C side during
> + // the whole QEMU life.
> + &*wrapper_ptr
> +};
next prev parent reply other threads:[~2025-08-07 13:51 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 12:30 [RFC 00/26] rust/memory: Integrate the vm-memory API from rust-vmm Zhao Liu
2025-08-07 12:30 ` [RFC 01/26] rust/hpet: Fix the error caused by vm-memory Zhao Liu
2025-08-07 13:52 ` Paolo Bonzini
2025-08-08 7:27 ` Zhao Liu
2025-08-07 12:30 ` [RFC 02/26] rust/cargo: Add the support for vm-memory Zhao Liu
2025-08-07 12:30 ` [RFC 03/26] subprojects: Add thiserror-impl crate Zhao Liu
2025-08-07 12:30 ` [RFC 04/26] subprojects: Add thiserror crate Zhao Liu
2025-08-07 12:30 ` [RFC 05/26] subprojects: Add winapi-i686-pc-windows-gnu crate Zhao Liu
2025-08-07 12:30 ` [RFC 06/26] subprojects: Add winapi-x86_64-pc-windows-gnu crate Zhao Liu
2025-08-07 12:30 ` [RFC 07/26] subprojects: Add winapi crate Zhao Liu
2025-08-07 13:17 ` Paolo Bonzini
2025-08-08 7:33 ` Zhao Liu
2025-08-07 12:30 ` [RFC 08/26] subprojects: Add vm-memory crate Zhao Liu
2025-08-07 12:30 ` [RFC 09/26] rust: Add vm-memory in meson Zhao Liu
2025-08-07 12:30 ` [RFC 10/26] subprojects/vm-memory: Patch vm-memory for QEMU memory backend Zhao Liu
2025-08-07 13:59 ` Paolo Bonzini
2025-08-08 8:17 ` Zhao Liu
2025-08-08 8:17 ` Paolo Bonzini
2025-08-08 8:51 ` Zhao Liu
2025-08-07 12:30 ` [RFC 11/26] rust/cargo: Specify the patched vm-memory crate Zhao Liu
2025-08-07 12:30 ` [RFC 12/26] rcu: Make rcu_read_lock & rcu_read_unlock not inline Zhao Liu
2025-08-07 13:54 ` Paolo Bonzini
2025-08-08 8:19 ` Zhao Liu
2025-08-07 12:30 ` [RFC 13/26] rust: Add RCU bindings Zhao Liu
2025-08-07 12:29 ` Manos Pitsidianakis
2025-08-07 13:38 ` Paolo Bonzini
2025-08-09 7:21 ` Zhao Liu
2025-08-09 9:13 ` Paolo Bonzini
2025-08-09 9:26 ` Manos Pitsidianakis
2025-08-12 10:43 ` Zhao Liu
2025-08-12 10:31 ` Zhao Liu
2025-08-07 12:30 ` [RFC 14/26] memory: Expose interfaces about Flatview reference count to Rust side Zhao Liu
2025-08-07 12:30 ` [RFC 15/26] memory: Rename address_space_lookup_region and expose it " Zhao Liu
2025-08-07 12:30 ` [RFC 16/26] memory: Make flatview_do_translate() return a pointer to MemoryRegionSection Zhao Liu
2025-08-07 13:57 ` Paolo Bonzini
2025-08-12 15:39 ` Zhao Liu
2025-08-12 15:42 ` Manos Pitsidianakis
2025-08-13 15:12 ` Zhao Liu
2025-08-12 19:23 ` Paolo Bonzini
2025-08-13 15:10 ` Zhao Liu
2025-08-07 12:30 ` [RFC 17/26] memory: Add a translation helper to return MemoryRegionSection Zhao Liu
2025-08-07 12:30 ` [RFC 18/26] memory: Rename flatview_access_allowed() to memory_region_access_allowed() Zhao Liu
2025-08-07 12:41 ` Manos Pitsidianakis
2025-08-07 12:30 ` [RFC 19/26] memory: Add MemoryRegionSection based misc helpers Zhao Liu
2025-08-07 12:30 ` [RFC 20/26] memory: Add wrappers of intermediate steps for read/write Zhao Liu
2025-08-07 12:30 ` [RFC 21/26] memory: Add store/load interfaces for Rust side Zhao Liu
2025-08-07 12:30 ` [RFC 22/26] rust/memory: Implement vm_memory::GuestMemoryRegion for MemoryRegionSection Zhao Liu
2025-08-07 12:30 ` [RFC 23/26] rust/memory: Implement vm_memory::GuestMemory for FlatView Zhao Liu
2025-08-07 12:30 ` [RFC 24/26] rust/memory: Provide AddressSpace bindings Zhao Liu
2025-08-07 13:50 ` Paolo Bonzini [this message]
2025-08-13 14:47 ` Zhao Liu
2025-08-07 12:30 ` [RFC 25/26] rust/memory: Add binding to check target endian Zhao Liu
2025-08-07 12:44 ` Manos Pitsidianakis
2025-08-13 14:48 ` Zhao Liu
2025-08-07 12:30 ` [RFC 26/26] rust/hpet: Use safe binding to access address space Zhao Liu
2025-08-07 12:42 ` [RFC 00/26] rust/memory: Integrate the vm-memory API from rust-vmm Zhao Liu
2025-08-07 14:13 ` Paolo Bonzini
2025-08-13 14:56 ` Zhao Liu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3ce35920-919b-4caf-87c5-b92bd603388a@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=chuanxiao.dong@intel.com \
--cc=dapeng1.mi@linux.intel.com \
--cc=david@redhat.com \
--cc=junjie.mao@hotmail.com \
--cc=manos.pitsidianakis@linaro.org \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-rust@nongnu.org \
--cc=thuth@redhat.com \
--cc=zhao1.liu@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).