From: Alice Ryhl <aliceryhl@google.com>
To: Benno Lossin <lossin@kernel.org>
Cc: "Lyude Paul" <lyude@redhat.com>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
"Andreas Hindborg" <a.hindborg@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>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>
Subject: Re: [PATCH v2 2/2] rust: time: Implement basic arithmetic operations for Delta
Date: Fri, 8 Aug 2025 08:56:50 +0000 [thread overview]
Message-ID: <aJW70pW5zVTPSrdj@google.com> (raw)
In-Reply-To: <DBWUBK3RSCMB.F1FJ5V6NCOJU@kernel.org>
On Fri, Aug 08, 2025 at 08:42:30AM +0200, Benno Lossin wrote:
> On Thu Aug 7, 2025 at 9:06 PM CEST, Lyude Paul wrote:
> > While rvkms is only going to be using a few of these, since Deltas are
> > basically the same as i64 it's easy enough to just implement all of the
> > basic arithmetic operations for Delta types.
> >
> > Keep in mind there's one quirk here - the kernel has no support for
> > i64 % i64 on 32 bit platforms, the closest we have is i64 % i32 through
> > div_s64_rem(). So, instead of implementing ops::Rem or ops::RemAssign we
> > simply provide Delta::rem_nanos().
>
> We could still provide the trait implementations on CONFIG_64BIT? WDYT?
>
> > +impl ops::Div for Delta {
> > + type Output = Self;
> > +
> > + #[inline]
> > + fn div(self, rhs: Self) -> Self::Output {
> > + #[cfg(CONFIG_64BIT)]
> > + {
>
> This pattern seems to be rather common in this patchset & in general I
> think I've also seen it elsewhere. We should think about adding a
> `if_cfg!` macro:
>
> Self {
> nanos: if_cfg! {
> if CONFIG_64BIT {
> self.nanos / rhs.nanos
> } else {
> unsafe { ... }
> }
> },
> }
>
> But we can do that later. I'll file a good-first-issue.
This kind of macro breaks rustfmt, so I wouldn't recommend it. I would
suggest just using the native Rust pattern rather than introduce even
more macros.
Alice
next prev parent reply other threads:[~2025-08-08 8:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 19:06 [PATCH v2 1/2] rust: time: Implement Add<Delta>/Sub<Delta> for Instant Lyude Paul
2025-08-07 19:06 ` [PATCH v2 2/2] rust: time: Implement basic arithmetic operations for Delta Lyude Paul
2025-08-08 6:42 ` Benno Lossin
2025-08-08 8:56 ` Alice Ryhl [this message]
2025-08-08 20:21 ` Benno Lossin
2025-08-08 9:26 ` Andreas Hindborg
2025-08-08 20:22 ` Benno Lossin
2025-08-10 7:18 ` Andreas Hindborg
2025-08-08 9:19 ` Andreas Hindborg
2025-08-08 22:44 ` Lyude Paul
2025-08-08 6:34 ` [PATCH v2 1/2] rust: time: Implement Add<Delta>/Sub<Delta> for Instant Benno Lossin
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=aJW70pW5zVTPSrdj@google.com \
--to=aliceryhl@google.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.