qemu-rust.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Zhao Liu <zhao1.liu@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-rust@nongnu.org,
	manos.pitsidianakis@linaro.org
Subject: Re: [PATCH 1/7] rust: bql: add BqlRefCell::get_mut()
Date: Tue, 23 Sep 2025 23:12:33 +0800	[thread overview]
Message-ID: <aNK44f/1+VEiOUQs@intel.com> (raw)
In-Reply-To: <20250920142958.181910-2-pbonzini@redhat.com>

On Sat, Sep 20, 2025 at 04:29:52PM +0200, Paolo Bonzini wrote:
> Date: Sat, 20 Sep 2025 16:29:52 +0200
> From: Paolo Bonzini <pbonzini@redhat.com>
> Subject: [PATCH 1/7] rust: bql: add BqlRefCell::get_mut()
> X-Mailer: git-send-email 2.51.0
> 
> This method is rarely useful in QEMU due to the pervasiveness of
> shared references, but add it for when a &mut BqlRefCell<> is used.
> 
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
>  rust/bql/src/cell.rs | 19 +++++++++++++++++++
>  1 file changed, 19 insertions(+)
> 
> diff --git a/rust/bql/src/cell.rs b/rust/bql/src/cell.rs
> index 24ab294b60d..8a0c8c14ad4 100644
> --- a/rust/bql/src/cell.rs
> +++ b/rust/bql/src/cell.rs
> @@ -580,6 +580,25 @@ pub fn borrow_mut(&self) -> BqlRefMut<'_, T> {
>          }
>      }
>  
> +    /// Returns a mutable reference to the underlying data in this cell,
> +    /// while the owner already has a mutable reference to the cell.
> +    ///
> +    /// # Examples
> +    ///
> +    /// ```
> +    /// use bql::BqlRefCell;
> +    ///
> +    /// let mut c = BqlRefCell::new(5);
> +    ///
> +    /// *c.get_mut() = 10;
> +    /// ```
> +    #[inline]
> +    pub const fn get_mut(&mut self) -> &mut T {
> +        // SAFETY: there cannot be any outstanding borrow,
> +        // since `self` is mutably owned.
> +        unsafe { &mut *self.as_ptr() }

Why not use UnsafeCell::get_mut?

self.value.get_mut()

Regards,
Zhao


  reply	other threads:[~2025-09-23 14:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-20 14:29 [RFC PATCH 0/7] rust: migration: add high-level migration wrappers Paolo Bonzini
2025-09-20 14:29 ` [PATCH 1/7] rust: bql: add BqlRefCell::get_mut() Paolo Bonzini
2025-09-23 15:12   ` Zhao Liu [this message]
2025-09-24 12:14     ` Paolo Bonzini
2025-09-20 14:29 ` [PATCH 2/7] rust: move VMState from bql to migration Paolo Bonzini
2025-09-23 14:46   ` Zhao Liu
2025-09-20 14:29 ` [PATCH 3/7] rust: migration: extract vmstate_fields_ref Paolo Bonzini
2025-09-24 15:21   ` Zhao Liu
2025-09-24 15:27     ` Zhao Liu
2025-09-25  9:24       ` Paolo Bonzini
2025-09-20 14:29 ` [PATCH 4/7] rust: migration: add high-level migration wrappers Paolo Bonzini
2025-09-25  9:05   ` Zhao Liu
2025-09-25  9:26     ` Paolo Bonzini
2025-09-20 14:29 ` [PATCH 5/7] rust: qemu-macros: add ToMigrationState derive macro Paolo Bonzini
2025-09-25 12:35   ` Zhao Liu
2025-09-25 16:56     ` Paolo Bonzini
2025-09-20 14:29 ` [PATCH 6/7] rust: migration: implement ToMigrationState for Timer Paolo Bonzini
2025-09-29 16:12   ` Zhao Liu
2025-09-29 16:11     ` Paolo Bonzini
2025-09-20 14:29 ` [PATCH 7/7] rust: migration: implement ToMigrationState as part of impl_vmstate_bitsized Paolo Bonzini
2025-09-30  6:53   ` 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=aNK44f/1+VEiOUQs@intel.com \
    --to=zhao1.liu@intel.com \
    --cc=manos.pitsidianakis@linaro.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-rust@nongnu.org \
    /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).