From: FUJITA Tomonori <tomo@flapping.org>
To: a.hindborg@kernel.org, ojeda@kernel.org
Cc: acourbot@nvidia.com, aliceryhl@google.com,
anna-maria@linutronix.de, bjorn3_gh@protonmail.com,
boqun@kernel.org, dakr@kernel.org, daniel.almeida@collabora.com,
frederic@kernel.org, gary@garyguo.net, jstultz@google.com,
lossin@kernel.org, lyude@redhat.com, sboyd@kernel.org,
tamird@kernel.org, tglx@kernel.org, tmgross@umich.edu,
work@onurozkan.dev, rust-for-linux@vger.kernel.org,
FUJITA Tomonori <fujita.tomonori@gmail.com>
Subject: [PATCH v1 1/2] rust: time: add example and KUnit test for Delta::as_millis_ceil()
Date: Wed, 12 Aug 2026 00:01:46 +0900 [thread overview]
Message-ID: <20260811150147.1360102-2-tomo@flapping.org> (raw)
In-Reply-To: <20260811150147.1360102-1-tomo@flapping.org>
From: FUJITA Tomonori <fujita.tomonori@gmail.com>
Add an example showing that the value is rounded towards positive
infinity, for both positive and negative spans.
as_millis_ceil() uses the same idiom as as_micros_ceil(), which dropped
the rounding bias near i64::MAX before commit ec90dfcf05f0 ("rust: time:
fix as_micros_ceil() rounding near i64::MAX"), so add a KUnit test for
the i64::MAX and i64::MIN extremes.
Signed-off-by: FUJITA Tomonori <fujita.tomonori@gmail.com>
---
rust/kernel/Kconfig.test | 10 ++++++++++
rust/kernel/time.rs | 42 ++++++++++++++++++++++++++++++++++++++++
2 files changed, 52 insertions(+)
diff --git a/rust/kernel/Kconfig.test b/rust/kernel/Kconfig.test
index e6a5c7a795f0..0087749995d2 100644
--- a/rust/kernel/Kconfig.test
+++ b/rust/kernel/Kconfig.test
@@ -83,4 +83,14 @@ config RUST_BITFIELD_KUNIT_TEST
If unsure, say N.
+config RUST_TIME_KUNIT_TEST
+ bool "KUnit tests for the Rust time API" if !KUNIT_ALL_TESTS
+ default KUNIT_ALL_TESTS
+ help
+ This option enables KUnit tests for the Rust time API.
+ These are only for development and testing, not for regular
+ kernel use cases.
+
+ If unsure, say N.
+
endif
diff --git a/rust/kernel/time.rs b/rust/kernel/time.rs
index 6c0a5e8090d0..b0b43ad3aa47 100644
--- a/rust/kernel/time.rs
+++ b/rust/kernel/time.rs
@@ -530,6 +530,21 @@ pub fn as_millis(self) -> i64 {
/// Return the smallest number of milliseconds greater than or equal
/// to the value in the [`Delta`].
+ ///
+ /// # Examples
+ ///
+ /// ```
+ /// use kernel::time::Delta;
+ ///
+ /// // Whole milliseconds are returned as-is.
+ /// assert_eq!(Delta::from_millis(2).as_millis_ceil(), 2);
+ /// assert_eq!(Delta::from_nanos(1_000_000).as_millis_ceil(), 1);
+ /// assert_eq!(Delta::from_nanos(-1_000_000).as_millis_ceil(), -1);
+ ///
+ /// // Anything else is rounded towards positive infinity.
+ /// assert_eq!(Delta::from_nanos(1_000_001).as_millis_ceil(), 2);
+ /// assert_eq!(Delta::from_nanos(-1_000_001).as_millis_ceil(), -1);
+ /// ```
#[inline]
pub fn as_millis_ceil(self) -> i64 {
// Only positive values need to be rounded up: truncating division already
@@ -580,3 +595,30 @@ pub fn rem_nanos(self, dividend: i32) -> Self {
}
}
}
+
+#[cfg(CONFIG_RUST_TIME_KUNIT_TEST)]
+#[macros::kunit_tests(rust_kernel_time)]
+mod tests {
+ use super::*;
+
+ /// `i64::MAX` nanoseconds in milliseconds, rounded towards positive infinity.
+ const MAX_MILLIS_CEIL: i64 = 9_223_372_036_855;
+
+ /// `i64::MIN` nanoseconds in milliseconds, rounded towards positive infinity.
+ const MIN_MILLIS_CEIL: i64 = -9_223_372_036_854;
+
+ #[test]
+ fn as_millis_ceil_extremes() {
+ // The rounding bias must survive near `i64::MAX`.
+ assert_eq!(
+ Delta::from_nanos(i64::MAX).as_millis_ceil(),
+ MAX_MILLIS_CEIL
+ );
+
+ // No bias is applied to negative values, so `i64::MIN` cannot overflow.
+ assert_eq!(
+ Delta::from_nanos(i64::MIN).as_millis_ceil(),
+ MIN_MILLIS_CEIL
+ );
+ }
+}
--
2.43.0
next prev parent reply other threads:[~2026-08-11 15:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 15:01 [PATCH v1 0/2] Add Delta::to_jiffies_timeout() with tests FUJITA Tomonori
2026-08-11 15:01 ` FUJITA Tomonori [this message]
2026-08-11 15:01 ` [PATCH v1 2/2] rust: time: add Delta::to_jiffies_timeout() for timeout conversion FUJITA Tomonori
2026-08-11 16:44 ` Gary Guo
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=20260811150147.1360102-2-tomo@flapping.org \
--to=tomo@flapping.org \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=anna-maria@linutronix.de \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=frederic@kernel.org \
--cc=fujita.tomonori@gmail.com \
--cc=gary@garyguo.net \
--cc=jstultz@google.com \
--cc=lossin@kernel.org \
--cc=lyude@redhat.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=tamird@kernel.org \
--cc=tglx@kernel.org \
--cc=tmgross@umich.edu \
--cc=work@onurozkan.dev \
/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