[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250711.152857.1107725157402630466.fujita.tomonori@gmail.com>
Date: Fri, 11 Jul 2025 15:28:57 +0900 (JST)
From: FUJITA Tomonori <fujita.tomonori@...il.com>
To: lyude@...hat.com
Cc: rust-for-linux@...r.kernel.org, fujita.tomonori@...il.com,
a.hindborg@...nel.org, boqun.feng@...il.com, frederic@...nel.org,
tglx@...utronix.de, anna-maria@...utronix.de, jstultz@...gle.com,
sboyd@...nel.org, ojeda@...nel.org, alex.gaynor@...il.com,
gary@...yguo.net, bjorn3_gh@...tonmail.com, lossin@...nel.org,
aliceryhl@...gle.com, tmgross@...ch.edu, dakr@...nel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] rust: time: Pass correct timer mode ID to
hrtimer_start_range_ns
On Thu, 10 Jul 2025 18:51:13 -0400
Lyude Paul <lyude@...hat.com> wrote:
> While rebasing rvkms I noticed that timers I was setting seemed to have
> pretty random timer values that amounted slightly over 2x the time value I
> set each time. After a lot of debugging, I finally managed to figure out
> why: it seems that since we moved to Instant and Delta, we mistakenly
> began passing the clocksource ID to hrtimer_start_range_ns, when we should
> be passing the timer mode instead. Presumably, this works fine for simple
> relative timers - but immediately breaks on other types of timers.
>
> So, fix this by passing the ID for the timer mode instead.
>
> Signed-off-by: Lyude Paul <lyude@...hat.com>
> Cc: FUJITA Tomonori <fujita.tomonori@...il.com>
> Fixes: fcc1dd8c8656 ("rust: time: Make HasHrTimer generic over HrTimerMode")
> ---
> rust/kernel/time/hrtimer.rs | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Ah, my bad! Thanks a lot for the fix.
Reviewed-by: FUJITA Tomonori <fujita.tomonori@...il.com>
Powered by blists - more mailing lists