[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87jz4fi72a.fsf@kernel.org>
Date: Fri, 11 Jul 2025 08:18:37 +0200
From: Andreas Hindborg <a.hindborg@...nel.org>
To: "Lyude Paul" <lyude@...hat.com>
Cc: <rust-for-linux@...r.kernel.org>, "FUJITA Tomonori"
<fujita.tomonori@...il.com>, "Boqun Feng" <boqun.feng@...il.com>,
"Frederic Weisbecker" <frederic@...nel.org>, "Thomas Gleixner"
<tglx@...utronix.de>, "Anna-Maria Behnsen" <anna-maria@...utronix.de>,
"John Stultz" <jstultz@...gle.com>, "Stephen Boyd" <sboyd@...nel.org>,
"Miguel Ojeda" <ojeda@...nel.org>, "Alex Gaynor"
<alex.gaynor@...il.com>, "Gary Guo" <gary@...yguo.net>, Björn Roy Baron
<bjorn3_gh@...tonmail.com>, "Benno Lossin" <lossin@...nel.org>, "Alice
Ryhl" <aliceryhl@...gle.com>, "Trevor Gross" <tmgross@...ch.edu>,
"Danilo Krummrich" <dakr@...nel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] rust: time: Pass correct timer mode ID to
hrtimer_start_range_ns
"Lyude Paul" <lyude@...hat.com> writes:
> 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")
Wow, thanks! Miguel, can you take this through rust-fixes?
Acked-by: Andreas Hindborg <a.hindborg@...nel.org>
Best regards,
Andreas Hindborg
Powered by blists - more mailing lists