From: FUJITA Tomonori <fujita.tomonori@gmail.com>
To: dakr@kernel.org, aliceryhl@google.com,
daniel.almeida@collabora.com, a.hindborg@kernel.org,
alex.gaynor@gmail.com, ojeda@kernel.org
Cc: anna-maria@linutronix.de, bjorn3_gh@protonmail.com,
boqun.feng@gmail.com, frederic@kernel.org, gary@garyguo.net,
jstultz@google.com, linux-kernel@vger.kernel.org,
lossin@kernel.org, lyude@redhat.com,
rust-for-linux@vger.kernel.org, sboyd@kernel.org,
tglx@linutronix.de, tmgross@umich.edu
Subject: [PATCH v2 0/2] Add read_poll_count_atomic support
Date: Tue, 21 Oct 2025 16:11:44 +0900 [thread overview]
Message-ID: <20251021071146.2357069-1-fujita.tomonori@gmail.com> (raw)
Add read_poll_count_atomic function which polls periodically until a
condition is met, an error occurs, or the attempt limit is reached.
This helper is used to wait for a condition in atomic context,
mirroring the C's read_poll_timeout_atomic().
In atomic context, the timekeeping infrastructure is unavailable, so
reliable time-based timeouts cannot be implemented. So instead, the
helper accepts a maximum number of attempts and busy-waits (udelay +
cpu_relax) between tries.
v1: https://lore.kernel.org/lkml/20250821035710.3692455-1-fujita.tomonori@gmail.com/
- use the attempt limit instead of timeout
- rename the function to read_poll_count_atomic
- add the comment about C's udelay behavior.
FUJITA Tomonori (2):
rust: add udelay() function
rust: Add read_poll_count_atomic function
rust/helpers/time.c | 5 +++
rust/kernel/io/poll.rs | 80 ++++++++++++++++++++++++++++++++++++++-
rust/kernel/time/delay.rs | 37 ++++++++++++++++++
3 files changed, 121 insertions(+), 1 deletion(-)
base-commit: e6901808a3b28d8bdabfa98a618b2eab6f8798e8
--
2.43.0
next reply other threads:[~2025-10-21 9:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 7:11 FUJITA Tomonori [this message]
2025-10-21 7:11 ` [PATCH v2 1/2] rust: add udelay() function FUJITA Tomonori
2025-10-21 12:08 ` Danilo Krummrich
2025-10-21 14:39 ` Miguel Ojeda
2025-10-21 14:46 ` Danilo Krummrich
2025-10-21 14:58 ` Miguel Ojeda
2025-10-21 15:09 ` Danilo Krummrich
2025-10-21 15:13 ` Miguel Ojeda
2025-10-21 15:20 ` Danilo Krummrich
2025-10-22 10:32 ` FUJITA Tomonori
2025-10-22 14:11 ` Alice Ryhl
2025-10-23 5:19 ` FUJITA Tomonori
2025-10-24 8:23 ` Andreas Hindborg
2025-10-24 8:20 ` Andreas Hindborg
2025-10-24 9:27 ` Alice Ryhl
2025-10-24 19:05 ` Miguel Ojeda
2025-10-26 13:11 ` FUJITA Tomonori
2025-10-26 14:49 ` Miguel Ojeda
2025-10-21 7:11 ` [PATCH v2 2/2] rust: Add read_poll_count_atomic function FUJITA Tomonori
2025-10-21 12:35 ` Danilo Krummrich
2025-10-21 14:05 ` Alice Ryhl
2025-10-21 16:02 ` Danilo Krummrich
2025-10-22 11:27 ` FUJITA Tomonori
2025-10-24 8:25 ` Andreas Hindborg
2025-10-24 9:19 ` Alice Ryhl
2025-10-23 5:24 ` 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=20251021071146.2357069-1-fujita.tomonori@gmail.com \
--to=fujita.tomonori@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=anna-maria@linutronix.de \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).