From: Andreas Hindborg <a.hindborg@kernel.org>
To: "Lyude Paul" <lyude@redhat.com>
Cc: rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
"Boqun Feng" <boqun.feng@gmail.com>,
"FUJITA Tomonori" <fujita.tomonori@gmail.com>,
"Frederic Weisbecker" <frederic@kernel.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Anna-Maria Behnsen" <anna-maria@linutronix.de>,
"John Stultz" <jstultz@google.com>,
"Stephen Boyd" <sboyd@kernel.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>
Subject: Re: [PATCH v5 7/7] rust: hrtimer: Add forward_now() to HrTimer and HrTimerCallbackContext
Date: Tue, 17 Jun 2025 13:34:21 +0200 [thread overview]
Message-ID: <87jz5aa9fm.fsf@kernel.org> (raw)
In-Reply-To: <20250613232754.451450-8-lyude@redhat.com> (Lyude Paul's message of "Fri, 13 Jun 2025 19:22:28 -0400")
"Lyude Paul" <lyude@redhat.com> writes:
> Using the HrTimer::raw_time_cb() function, we can now add an equivalent to
You called it `raw_cb_time`.
> hrtimer_forward_now() to both HrTimer and HrTimerCallbackContext.
>
> Signed-off-by: Lyude Paul <lyude@redhat.com>
>
> ---
> V2:
> * Change from Ktime to Delta
> * Make sure that forward_now() takes a mutable reference to the timer
> struct
> * Reword this to point out that we're adding forward_now() to both callback
> context and mutable timer reference
> * Rename interval to duration
>
> V4:
> * Fix rust documentation for HrTimerCallbackContext (forgot to update both
> forward_now() declarations)
> * Use Pin<&mut Self> for context-less forward.
>
> Signed-off-by: Lyude Paul <lyude@redhat.com>
> ---
> rust/kernel/time/hrtimer.rs | 58 ++++++++++++++++++++++++++++++++++++-
> 1 file changed, 57 insertions(+), 1 deletion(-)
>
> diff --git a/rust/kernel/time/hrtimer.rs b/rust/kernel/time/hrtimer.rs
> index 79d86e1099a1e..0908359b0550a 100644
> --- a/rust/kernel/time/hrtimer.rs
> +++ b/rust/kernel/time/hrtimer.rs
> @@ -201,7 +201,6 @@ unsafe fn raw_forward(self_ptr: *mut Self, now: HrTimerInstant<T>, interval: Del
> /// - The caller must ensure that the `hrtimer_clock_base` cannot possibly change in the context
> /// this function is being called in. This means either exclusive access to `self_ptr` is
> /// required, or we must be from within the timer callback context of `self_ptr`.
> - #[expect(unused)]
> unsafe fn raw_cb_time(self_ptr: *const Self) -> HrTimerInstant<T>
> where
> T: HasHrTimer<T>,
> @@ -243,6 +242,44 @@ pub fn forward(self: Pin<&mut Self>, now: HrTimerInstant<T>, interval: Delta) ->
> // exclusive access to it - fulfilling the requirements of the C API.
> unsafe { Self::raw_forward(self.get_unchecked_mut(), now, interval) }
> }
> +
> + /// Conditionally forward the timer.
> + ///
> + /// This is a variant of [`forward()`](Self::forward) that uses an interval after the current
> + /// time of the base clock for the [`HrTimer`].
> + pub fn forward_now(self: Pin<&mut Self>, interval: Delta) -> u64
> + where
> + T: HasHrTimer<T>,
> + {
> + // SAFETY: `self` is a mutable reference, guaranteeing it is both a valid pointer to Self
> + // and that we also have exclusive access to `self`.
> + let now = unsafe { Self::raw_cb_time(&*self.as_ref()) };
> +
> + self.forward(now, interval)
> + }
> +
> + /// Return the time expiry for this [`HrTimer`].
> + ///
> + /// This value should only be used as a snapshot, as the actual expiry time could change after
> + /// this function is called.
> + pub fn expires(&self) -> HrTimerInstant<T>
Commit message does not mention this method.
Best regards,
Andreas Hindborg
prev parent reply other threads:[~2025-06-17 11:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 23:22 [PATCH v5 0/7] rust/hrtimer: Various hrtimer + time additions Lyude Paul
2025-06-13 23:22 ` [PATCH v5 1/7] rust: hrtimer: Document the return value for HrTimerHandle::cancel() Lyude Paul
2025-06-17 11:35 ` Andreas Hindborg
2025-06-13 23:22 ` [PATCH v5 2/7] rust: hrtimer: Add HrTimerInstant Lyude Paul
2025-06-17 11:35 ` Andreas Hindborg
2025-06-13 23:22 ` [PATCH v5 3/7] rust: hrtimer: Add HrTimer::raw_forward() and forward() Lyude Paul
2025-06-17 11:06 ` Andreas Hindborg
2025-06-13 23:22 ` [PATCH v5 4/7] rust: hrtimer: Add HrTimerCallbackContext and ::forward() Lyude Paul
2025-06-17 11:18 ` Andreas Hindborg
2025-06-13 23:22 ` [PATCH v5 5/7] rust: time: Add Instant::from_nanos() Lyude Paul
2025-06-13 23:22 ` [PATCH v5 6/7] rust: hrtimer: Add HrTimer::raw_cb_time() Lyude Paul
2025-06-17 11:30 ` Andreas Hindborg
2025-06-13 23:22 ` [PATCH v5 7/7] rust: hrtimer: Add forward_now() to HrTimer and HrTimerCallbackContext Lyude Paul
2025-06-14 1:58 ` FUJITA Tomonori
2025-06-17 11:34 ` Andreas Hindborg [this message]
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=87jz5aa9fm.fsf@kernel.org \
--to=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=anna-maria@linutronix.de \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=frederic@kernel.org \
--cc=fujita.tomonori@gmail.com \
--cc=gary@garyguo.net \
--cc=jstultz@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=lyude@redhat.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=sboyd@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).