From: Andreas Hindborg <a.hindborg@kernel.org>
To: "Lyude Paul" <lyude@redhat.com>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Anna-Maria Behnsen" <anna-maria@linutronix.de>,
"Frederic Weisbecker" <frederic@kernel.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Danilo Krummrich" <dakr@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Guangbo Cui" <2407018371@qq.com>,
"Dirk Behme" <dirk.behme@gmail.com>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"Tamir Duberstein" <tamird@gmail.com>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 04/14] rust: hrtimer: implement `HrTimerPointer` for `Arc`
Date: Sat, 15 Feb 2025 11:35:08 +0100 [thread overview]
Message-ID: <874j0vv6lf.fsf@kernel.org> (raw)
In-Reply-To: <4ce7b3dcbac5ba71d3f58d72f3c01d250da784e7.camel@redhat.com> (Lyude Paul's message of "Mon, 10 Feb 2025 17:28:45 -0500")
"Lyude Paul" <lyude@redhat.com> writes:
> On Mon, 2025-02-03 at 16:07 +0100, Andreas Hindborg wrote:
>> This patch allows the use of intrusive `hrtimer` fields in structs that are
>> managed by an `Arc`.
>>
>> Signed-off-by: Andreas Hindborg <a.hindborg@kernel.org>
>> ---
>> rust/kernel/time/hrtimer.rs | 3 +-
>> rust/kernel/time/hrtimer/arc.rs | 89 +++++++++++++++++++++++++++++++++++++++++
>> 2 files changed, 91 insertions(+), 1 deletion(-)
>>
>> diff --git a/rust/kernel/time/hrtimer.rs b/rust/kernel/time/hrtimer.rs
>> index a6332924efabd40c475a112bbc434db77596a16f..3494c00481a4bd25735edf44b6bdcbec9810243e 100644
>> --- a/rust/kernel/time/hrtimer.rs
>> +++ b/rust/kernel/time/hrtimer.rs
>> @@ -119,7 +119,6 @@ unsafe fn raw_get(ptr: *const Self) -> *mut bindings::hrtimer {
>> /// # Safety
>> ///
>> /// `self_ptr` must point to a valid `Self`.
>> - #[allow(dead_code)]
>> pub(crate) unsafe fn raw_cancel(self_ptr: *const Self) -> bool {
>> // SAFETY: timer_ptr points to an allocation of at least `HrTimer` size.
>> let c_timer_ptr = unsafe { HrTimer::raw_get(self_ptr) };
>> @@ -310,3 +309,5 @@ unsafe fn raw_get_timer(ptr: *const Self) ->
>> }
>> }
>> }
>> +
>> +mod arc;
>> diff --git a/rust/kernel/time/hrtimer/arc.rs b/rust/kernel/time/hrtimer/arc.rs
>> new file mode 100644
>> index 0000000000000000000000000000000000000000..d1c90631d00362bdc38be1ccc75429ae294ab544
>> --- /dev/null
>> +++ b/rust/kernel/time/hrtimer/arc.rs
>> @@ -0,0 +1,89 @@
>> +// SPDX-License-Identifier: GPL-2.0
>> +
>> +use super::HasHrTimer;
>> +use super::HrTimer;
>> +use super::HrTimerCallback;
>> +use super::HrTimerHandle;
>> +use super::HrTimerPointer;
>> +use super::RawHrTimerCallback;
>> +use crate::sync::Arc;
>> +use crate::sync::ArcBorrow;
>> +use crate::time::Ktime;
>> +
>> +/// A handle for an `Arc<HasHrTimer<T>>` returned by a call to
>> +/// [`HrTimerPointer::start`].
>> +pub struct ArcHrTimerHandle<T>
>> +where
>> + T: HasHrTimer<T>,
>> +{
>> + pub(crate) inner: Arc<T>,
>> +}
>> +
>
> BTW - I noticed the other day that it doesn't seem like we actually expose
> this type to users anywhere, even though we would want access to it for
> storing the timer handle in structures
>
Thanks for noticing! I'll make sure to `pub use` then handles in the
parent module.
Best regards,
Andreas Hindborg
next prev parent reply other threads:[~2025-02-15 10:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 15:07 [PATCH v7 00/14] hrtimer Rust API Andreas Hindborg
2025-02-03 15:07 ` [PATCH v7 01/14] rust: time: Add Ktime::from_ns() Andreas Hindborg
2025-02-03 15:07 ` [PATCH v7 02/14] rust: hrtimer: introduce hrtimer support Andreas Hindborg
2025-02-03 15:07 ` [PATCH v7 03/14] rust: sync: add `Arc::as_ptr` Andreas Hindborg
2025-02-03 15:07 ` [PATCH v7 04/14] rust: hrtimer: implement `HrTimerPointer` for `Arc` Andreas Hindborg
2025-02-10 22:28 ` Lyude Paul
2025-02-15 10:35 ` Andreas Hindborg [this message]
2025-02-03 15:07 ` [PATCH v7 05/14] rust: hrtimer: allow timer restart from timer handler Andreas Hindborg
2025-02-03 15:07 ` [PATCH v7 06/14] rust: hrtimer: add `UnsafeHrTimerPointer` Andreas Hindborg
2025-02-03 15:07 ` [PATCH v7 07/14] rust: hrtimer: add `hrtimer::ScopedHrTimerPointer` Andreas Hindborg
2025-02-03 15:07 ` [PATCH v7 08/14] rust: hrtimer: implement `UnsafeHrTimerPointer` for `Pin<&T>` Andreas Hindborg
2025-02-03 15:07 ` [PATCH v7 09/14] rust: hrtimer: implement `UnsafeHrTimerPointer` for `Pin<&mut T>` Andreas Hindborg
2025-02-03 15:07 ` [PATCH v7 10/14] rust: alloc: add `Box::into_pin` Andreas Hindborg
2025-02-03 15:07 ` [PATCH v7 11/14] rust: hrtimer: implement `HrTimerPointer` for `Pin<Box<T>>` Andreas Hindborg
2025-02-03 15:07 ` [PATCH v7 12/14] rust: hrtimer: add `HrTimerMode` Andreas Hindborg
2025-02-03 15:07 ` [PATCH v7 13/14] rust: hrtimer: add clocksource selection through `ClockSource` Andreas Hindborg
2025-02-03 15:08 ` [PATCH v7 14/14] rust: hrtimer: add maintainer entry Andreas Hindborg
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=874j0vv6lf.fsf@kernel.org \
--to=a.hindborg@kernel.org \
--cc=2407018371@qq.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=anna-maria@linutronix.de \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=dirk.behme@gmail.com \
--cc=frederic@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tamird@gmail.com \
--cc=tglx@linutronix.de \
--cc=tmgross@umich.edu \
/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