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 v9 04/13] rust: hrtimer: allow timer restart from timer handler
Date: Wed, 26 Feb 2025 14:43:49 +0100 [thread overview]
Message-ID: <878qpsvn1m.fsf@kernel.org> (raw)
In-Reply-To: <6c2a299ec594fbaae294037e36c78cb37aaa7f33.camel@redhat.com> (Lyude Paul's message of "Tue, 25 Feb 2025 16:46:56 -0500")
"Lyude Paul" <lyude@redhat.com> writes:
> On Tue, 2025-02-25 at 09:58 +0100, Andreas Hindborg wrote:
>> "Lyude Paul" <lyude@redhat.com> writes:
>>
>> > On Mon, 2025-02-24 at 13:03 +0100, Andreas Hindborg wrote:
>> >
>> > Also, I feel like I might have asked this a few versions ago so hopefully i'm
>> > not asking again: but what's the reason for us not just using the
>> > discriminants of `HrTimerRestart` here:
>> >
>> > /// Restart policy for timers.
>> > #[repr(u32)]
>> > pub enum HrTimerRestart {
>> > /// Timer should not be restarted.
>> > NoRestart = bindings::hrtimer_restart_HRTIMER_NORESTART,
>> > /// Timer should be restarted.
>> > Restart = bindings::hrtimer_restart_HRTIMER_RESTART,
>> > }
>>
>> I forget if we discussed this, but it does not make much of a
>> difference, does it?
>>
>> With a Rust enum, we get a smaller storage type maybe with better
>> support for niche optimizations? And then pay a bit more for conversion.
>> All in all, I don't think it makes much difference.
>
> No idea about performance wise, but I -think- it would actually cut down on
> the code that you need - particularly for the larger enums here. Mainly
> because you only would need to manually specify each variant for converting
> from bindings::hrtimer_restart to HrTimerRestart, but not the other way
> around:
>
> /// Restart policy for timers.
> #[repr(u32)]
> pub enum HrTimerRestart {
> /// Timer should not be restarted.
> NoRestart = bindings::hrtimer_restart_HRTIMER_NORESTART,
> /// Timer should be restarted.
> Restart = bindings::hrtimer_restart_HRTIMER_RESTART,
> }
>
> impl From<bindings::hrtimer_restart> for HrTimerRestart {
> fn from(value: u32) -> Self {
> match value {
> bindings::hrtimer_restart_HRTIMER_NORESTART => Self::NoRestart,
> _ => Self::Restart,
> }
> }
> }
>
> impl From<HrTimerRestart> for bindings::hrtimer_restart {
> fn from(value: HrTimerRestart) -> Self {
> value as Self
> }
> }
I was implementing this, and it is fine for `HrTimerRestart`, but for
`HrTimerMode` it does not work out. We have multiple flags with the same
value:
error[E0081]: discriminant value `2` assigned more than once
--> /home/aeh/src/linux-rust/hrtimer/rust/kernel/time/hrtimer.rs:689:1
|
689 | pub enum HrTimerMode {
| ^^^^^^^^^^^^^^^^^^^^
...
695 | Pinned = bindings::hrtimer_mode_HRTIMER_MODE_PINNED,
| ------------------------------------------ `2` assigned here
...
702 | AbsolutePinned = bindings::hrtimer_mode_HRTIMER_MODE_ABS_PINNED,
| ---------------------------------------------- `2` assigned here
Which is unfortunate. I'll keep the old style for this one and convert
the others where applicable.
Best regards,
Andreas Hindborg
next prev parent reply other threads:[~2025-02-26 13:44 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 12:03 [PATCH v9 00/13] hrtimer Rust API Andreas Hindborg
2025-02-24 12:03 ` [PATCH v9 01/13] rust: hrtimer: introduce hrtimer support Andreas Hindborg
2025-02-24 13:19 ` Andreas Hindborg
2025-02-24 15:46 ` Boqun Feng
2025-02-24 16:23 ` Miguel Ojeda
2025-02-24 16:31 ` Boqun Feng
2025-02-24 16:45 ` Miguel Ojeda
2025-02-24 17:01 ` Boqun Feng
2025-02-24 18:58 ` Andreas Hindborg
2025-02-24 19:18 ` Boqun Feng
2025-02-24 19:52 ` Andreas Hindborg
2025-02-24 20:22 ` Boqun Feng
2025-02-25 5:50 ` Andreas Hindborg
2025-02-26 16:31 ` Frederic Weisbecker
2025-02-26 19:41 ` Andreas Hindborg
2025-02-24 20:04 ` Tamir Duberstein
2025-02-25 8:52 ` Andreas Hindborg
2025-02-25 15:37 ` Tamir Duberstein
2025-02-25 19:12 ` Andreas Hindborg
2025-02-25 20:13 ` Tamir Duberstein
2025-02-26 11:48 ` Andreas Hindborg
2025-02-26 15:29 ` Tamir Duberstein
2025-03-07 9:09 ` Andreas Hindborg
2025-02-25 11:36 ` Markus Elfring
2025-02-25 12:13 ` Andreas Hindborg
2025-02-27 8:31 ` Thomas Gleixner
2025-02-27 10:44 ` Andreas Hindborg
2025-02-24 12:03 ` [PATCH v9 02/13] rust: sync: add `Arc::as_ptr` Andreas Hindborg
2025-02-24 12:03 ` [PATCH v9 03/13] rust: hrtimer: implement `HrTimerPointer` for `Arc` Andreas Hindborg
2025-02-24 23:13 ` Lyude Paul
2025-02-24 12:03 ` [PATCH v9 04/13] rust: hrtimer: allow timer restart from timer handler Andreas Hindborg
2025-02-24 23:23 ` Lyude Paul
2025-02-25 8:58 ` Andreas Hindborg
2025-02-25 21:46 ` Lyude Paul
2025-02-26 13:43 ` Andreas Hindborg [this message]
2025-02-26 19:26 ` Lyude Paul
2025-02-24 12:03 ` [PATCH v9 05/13] rust: hrtimer: add `UnsafeHrTimerPointer` Andreas Hindborg
2025-02-24 23:24 ` Lyude Paul
2025-02-24 12:03 ` [PATCH v9 06/13] rust: hrtimer: add `hrtimer::ScopedHrTimerPointer` Andreas Hindborg
2025-02-24 23:25 ` Lyude Paul
2025-02-24 12:03 ` [PATCH v9 07/13] rust: hrtimer: implement `UnsafeHrTimerPointer` for `Pin<&T>` Andreas Hindborg
2025-02-24 23:32 ` Lyude Paul
2025-02-25 9:01 ` Andreas Hindborg
2025-02-24 12:03 ` [PATCH v9 08/13] rust: hrtimer: implement `UnsafeHrTimerPointer` for `Pin<&mut T>` Andreas Hindborg
2025-02-24 23:33 ` Lyude Paul
2025-02-24 12:03 ` [PATCH v9 09/13] rust: alloc: add `Box::into_pin` Andreas Hindborg
2025-02-24 23:34 ` Lyude Paul
2025-02-24 12:03 ` [PATCH v9 10/13] rust: hrtimer: implement `HrTimerPointer` for `Pin<Box<T>>` Andreas Hindborg
2025-02-24 23:37 ` Lyude Paul
2025-02-24 12:03 ` [PATCH v9 11/13] rust: hrtimer: add `HrTimerMode` Andreas Hindborg
2025-02-24 23:40 ` Lyude Paul
2025-02-25 9:04 ` Andreas Hindborg
2025-02-25 21:49 ` Lyude Paul
2025-02-24 12:03 ` [PATCH v9 12/13] rust: hrtimer: add clocksource selection through `ClockSource` Andreas Hindborg
2025-02-24 23:42 ` Lyude Paul
2025-02-27 9:11 ` Thomas Gleixner
2025-02-27 9:24 ` Thomas Gleixner
2025-02-27 11:18 ` Andreas Hindborg
2025-02-27 14:22 ` Thomas Gleixner
2025-02-27 16:03 ` Andreas Hindborg
2025-02-24 12:03 ` [PATCH v9 13/13] rust: hrtimer: add maintainer entry Andreas Hindborg
2025-02-24 15:44 ` Boqun Feng
2025-02-26 16:17 ` Frederic Weisbecker
2025-02-26 19:42 ` Andreas Hindborg
2025-02-26 19:49 ` Lyude Paul
2025-02-26 21:08 ` Andreas Hindborg
2025-02-27 9:12 ` Thomas Gleixner
2025-02-27 10:45 ` Andreas Hindborg
2025-02-24 23:43 ` Lyude Paul
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=878qpsvn1m.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