From: Paolo Bonzini <pbonzini@redhat.com>
To: Zhao Liu <zhao1.liu@intel.com>
Cc: qemu-devel@nongnu.org, qemu-rust@nongnu.org
Subject: Re: [PATCH 3/5] rust/hpet: remove BqlRefCell around HPETTimer
Date: Wed, 19 Nov 2025 23:28:31 +0100 [thread overview]
Message-ID: <91bf0b22-33c4-46f7-95fa-f634eb069ea7@redhat.com> (raw)
In-Reply-To: <aR3fhvpIsXRnQcj8@intel.com>
On 11/19/25 16:17, Zhao Liu wrote:
>> - fn init_timer_with_cell(cell: &BqlRefCell<Self>) {
>> - let mut timer = cell.borrow_mut();
>> - // SAFETY: HPETTimer is only used as part of HPETState, which is
>> - // always pinned.
>> - let qemu_timer = unsafe { Pin::new_unchecked(&mut timer.qemu_timer) };
>> - qemu_timer.init_full(None, CLOCK_VIRTUAL, Timer::NS, 0, timer_handler, cell);
>> + fn init_timer(timer: Pin<&mut Self>) {
>> + Timer::init_full(
>> + timer,
>> + None,
>> + CLOCK_VIRTUAL,
>> + Timer::NS,
>> + 0,
>> + timer_handler,
>> + |t| &mut t.qemu_timer,
>> + );
>> }
>
> I find this way could also work for BqlRefCell case:
>
> fn init_timer_with_cell(cell: &mut BqlRefCell<Self>) {
> // SAFETY: HPETTimer is only used as part of HPETState, which is
> // always pinned.
> let timer = unsafe { Pin::new_unchecked(cell) };
> Timer::init_full(
> timer,
> None,
> CLOCK_VIRTUAL,
> Timer::NS,
> 0,
> timer_handler,
> |t| {
> assert!(bql::is_locked());
> &mut t.get_mut().qemu_timer
> },
> );
> }
Yes, but I'm still not sure what the final shape will be... I don't like
this too much.
>
> So any other non-lockless timer can also use this interface to
> initialize their BqlRefCell<>.
>
> (BTW, I find BqlRefCell::get_mut() / as_ref() missed bql::is_locked().
> right?)
as_ptr() doesn't need it because the pointer can be dereferenced later.
As to get_mut()... I think if you are the only owner, you should have
the guarantee of being able to modify the content freely. This is true
even if your &mut came from interior mutability.
So, in the above case you only need &mut t.get_mut().qemu_timer.
> I think it may be better to add doc about how to use this for
> BqlRefCell<> case since there'll be no example after this patch.
next prev parent reply other threads:[~2025-11-19 22:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 8:47 [PATCH 0/5] rust/hpet: complete moving state out of HPETTimer Paolo Bonzini
2025-11-17 8:47 ` [PATCH 1/5] rust/hpet: move hidden registers to HPETTimerRegisters Paolo Bonzini
2025-11-18 8:35 ` Zhao Liu
2025-11-17 8:47 ` [PATCH 2/5] rust/hpet: move hpet_offset to HPETRegisters Paolo Bonzini
2025-11-18 13:54 ` Zhao Liu
2025-11-17 8:47 ` [PATCH 3/5] rust/hpet: remove BqlRefCell around HPETTimer Paolo Bonzini
2025-11-19 15:17 ` Zhao Liu
2025-11-19 22:28 ` Paolo Bonzini [this message]
2025-11-17 8:47 ` [PATCH 4/5] rust: migration: implement ToMigrationState for Timer Paolo Bonzini
2025-11-20 14:31 ` Zhao Liu
2025-11-17 8:47 ` [PATCH 5/5] rust/hpet: Apply Migratable<> wrapper and ToMigrationState Paolo Bonzini
2025-11-19 15:31 ` Zhao Liu
2025-11-19 15:59 ` [PATCH 0/5] rust/hpet: complete moving state out of HPETTimer 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=91bf0b22-33c4-46f7-95fa-f634eb069ea7@redhat.com \
--to=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-rust@nongnu.org \
--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).