linux-kernel - Re: [PATCH v11 6/8] MAINTAINERS: rust: Add new sections for DELAY/SLEEP and TIMEKEEPING API

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <877c41v7kf.fsf@kernel.org>
Date: Thu, 03 Apr 2025 12:54:40 +0200
From: Andreas Hindborg <a.hindborg@...nel.org>
To: "FUJITA Tomonori" <fujita.tomonori@...il.com>
Cc: <boqun.feng@...il.com>,  <tglx@...utronix.de>,
  <linux-kernel@...r.kernel.org>,  <rust-for-linux@...r.kernel.org>,
  <netdev@...r.kernel.org>,  <andrew@...n.ch>,  <hkallweit1@...il.com>,
  <tmgross@...ch.edu>,  <ojeda@...nel.org>,  <alex.gaynor@...il.com>,
  <gary@...yguo.net>,  <bjorn3_gh@...tonmail.com>,
  <benno.lossin@...ton.me>,  <a.hindborg@...sung.com>,
  <aliceryhl@...gle.com>,  <anna-maria@...utronix.de>,
  <frederic@...nel.org>,  <arnd@...db.de>,  <jstultz@...gle.com>,
  <sboyd@...nel.org>,  <mingo@...hat.com>,  <peterz@...radead.org>,
  <juri.lelli@...hat.com>,  <vincent.guittot@...aro.org>,
  <dietmar.eggemann@....com>,  <rostedt@...dmis.org>,
  <bsegall@...gle.com>,  <mgorman@...e.de>,  <vschneid@...hat.com>,
  <tgunders@...hat.com>,  <me@...enk.dev>,  <david.laight.linux@...il.com>
Subject: Re: [PATCH v11 6/8] MAINTAINERS: rust: Add new sections for
 DELAY/SLEEP and TIMEKEEPING API

"FUJITA Tomonori" <fujita.tomonori@...il.com> writes:

> On Mon, 31 Mar 2025 21:43:50 +0200
> Andreas Hindborg <a.hindborg@...nel.org> wrote:
>
>>>> If that is acceptable to everyone, it is very likely that I can pick 2-6
>>>> for v6.16.
>>>>
>>>
>>> You will need to fix something because patch 2-6 removes `Ktime` ;-)
>>
>> Yea, but `Instant` is almost a direct substitution, right? Anyway, Tomo
>> can send a new spin and change all the uses of Ktime, or I can do it. It
>> should be straight forward. Either way is fine with me.
>
> `Delta`? Not `Instant`.

It depends. Current hrtimer takes `Ktime` and supports
`HrTimerMode::Absolute` and `HrTimerMode::Relative`. With `Delta` and
`Instant` we should take `Instant` for `HrTimerMode::Absolute` and
`Delta` for `HrTimerMode::Relative`. The API needs to be modified a bit
to make that work though. Probably we need to make the start function
generic over the expiration type or something.

If you want to, you can fix that. If not, you can use `Instant` for the
relative case as well, and we shall interpret it as duration. Then I
will fix it up later. Your decision.

> All Ktime in hrtimer are passed to hrtimer_start_range_ns(), right?

Yes, that is where they end up.

> I'll send a new version shortly.

Great :)


Best regards,
Andreas Hindborg