From: FUJITA Tomonori <tomo@flapping.org>
To: boqun@kernel.org
Cc: tomo@flapping.org, mike@fireburn.co.uk, a.hindborg@kernel.org,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
ojeda@kernel.org, gary@garyguo.net, bjorn3_gh@protonmail.com,
lossin@kernel.org, aliceryhl@google.com, tmgross@umich.edu,
dakr@kernel.org, daniel.almeida@collabora.com,
frederic@kernel.org, tglx@kernel.org, anna-maria@linutronix.de,
jstultz@google.com, sboyd@kernel.org
Subject: Re: [PATCH 9/9] rust: time: add ktime_get_real_seconds
Date: Sat, 31 Oct 2026 09:39:29 +0900 (JST) [thread overview]
Message-ID: <20261031.093929.648818945104239611.tomo@flapping.org> (raw)
In-Reply-To: <auTpDD4GRiD00jP2@tardis.local>
On Fri, 30 Oct 2026 11:59:24 -0700
Boqun Feng <boqun@kernel.org> wrote:
> The way I see it is from kernel::time perspective, we still want to make
> sure the APIs are still in the same abstraction layer, a
> ktime_get_real_seconds() co-exists with Instant::now() as the public
> interface layer breaks that in my opinion. And the generic type
> parameter should be flexible enough to avoid introduce anything we don't
> have a user yet.
OK. I sent a series that adds a unit parameter to `Instant` and a
seconds based `Instant` on top of it, with `Sub` and the other
arithmetic on `Instant<C, Nsec>` only:
https://lore.kernel.org/rust-for-linux/20261031003334.4161188-1-tomo@flapping.org/
What it costs is a new trait `InstantUnit` with a read function, a
second method on `ClockId`, and per-unit invariants on
`Instant`. Please take a look and tell me if this is fine.
next prev parent reply other threads:[~2026-10-31 0:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260826162851.2497-1-mike@fireburn.co.uk>
2026-08-26 16:28 ` [PATCH 1/9] rust: sync: completion: add single-shot and timed operations Mike Lothian
2026-08-26 16:28 ` [PATCH 2/9] rust: hrtimer: add ArcHrTimerHandle::restart Mike Lothian
2026-08-27 13:27 ` Andreas Hindborg
[not found] ` <3-IkUMhanJhClxwXLNvuF1-ncsHt6uM6GRmW78t81tKgo_5IO80fRJ9HZROE5RwlmxZhufdPXswcExj5j65ejw==@protonmail.internalid>
[not found] ` <CAHbf0-F-KNQu5NrFcUw1JOwaVQJq5hS+d9OHTmV3J2Pi+hfOqA@mail.gmail.com>
2026-08-31 16:54 ` Andreas Hindborg
2026-09-02 12:49 ` Mike Lothian
2026-08-26 16:28 ` [PATCH 3/9] rust: random: add a safe get_random_bytes wrapper Mike Lothian
2026-08-26 16:28 ` [PATCH 4/9] rust: xxhash: add a safe xxh64 wrapper Mike Lothian
2026-08-26 16:28 ` [PATCH 5/9] rust: workqueue: make OwnedQueue thread-safe Mike Lothian
2026-08-26 16:28 ` [PATCH 6/9] rust: io: add checked offset copy helpers Mike Lothian
2026-08-26 16:28 ` [PATCH 7/9] rust: hrtimer: expose interrupt state in hard callbacks Mike Lothian
2026-08-27 13:34 ` Andreas Hindborg
2026-08-26 16:28 ` [PATCH 8/9] rust: error: expose EPROTO Mike Lothian
2026-08-26 16:34 ` Miguel Ojeda
2026-08-26 16:28 ` [PATCH 9/9] rust: time: add ktime_get_real_seconds Mike Lothian
2026-08-27 13:39 ` Andreas Hindborg
2026-09-08 11:14 ` FUJITA Tomonori
2026-09-08 13:01 ` Andreas Hindborg
2026-10-30 7:57 ` Mike Lothian
2026-10-30 10:05 ` FUJITA Tomonori
2026-10-30 18:59 ` Boqun Feng
2026-10-31 0:39 ` FUJITA Tomonori [this message]
2026-09-08 11:19 ` FUJITA Tomonori
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=20261031.093929.648818945104239611.tomo@flapping.org \
--to=tomo@flapping.org \
--cc=a.hindborg@kernel.org \
--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=gary@garyguo.net \
--cc=jstultz@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=mike@fireburn.co.uk \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=tglx@kernel.org \
--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
all inboxes | Powered by JetHome®