From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Boqun Feng" <boqun.feng@gmail.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Alice Ryhl" <aliceryhl@google.com>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Benno Lossin" <lossin@kernel.org>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Danilo Krummrich" <dakr@kernel.org>,
"Gary Guo" <gary@garyguo.net>, "Miguel Ojeda" <ojeda@kernel.org>,
"Peter Zijlstra" <peterz@infradead.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Trevor Gross" <tmgross@umich.edu>,
"Viresh Kumar" <viresh.kumar@linaro.org>,
"Yury Norov" <yury.norov@gmail.com>
Cc: Vincent Guittot <vincent.guittot@linaro.org>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org
Subject: [PATCH V3 0/3] rust: Introduce CpuId and fix cpumask doctest
Date: Tue, 10 Jun 2025 18:51:55 +0530 [thread overview]
Message-ID: <cover.1749554685.git.viresh.kumar@linaro.org> (raw)
Hello,
Here is another attempt at fixing the cpumask doctest. This series creates a new
abstraction `CpuId`, which is used to write a cleaner cpumask example which
doesn't fail in those corner cases.
Rebased over v6.16-rc1 + [1].
V2->V3:
- Include the separately sent patch as 3/3 and clarify about `unstable` CpuId.
- Add few debug_assert!().
- Improved comments, commit log.
V1->V2:
- Introduce CpuId.
- Use CpuId in cpufreq, opp, cpumask abstractions.
- Fix cpumask example.
--
Viresh
[1] https://lore.kernel.org/all/4823a58093c6dfa20df62b5c18da613621b9716e.1749554599.git.viresh.kumar@linaro.org/
Viresh Kumar (3):
rust: cpu: Introduce CpuId abstraction
rust: Use CpuId in place of raw CPU numbers
rust: cpu: Add CpuId::current() to retrieve current CPU ID
MAINTAINERS | 1 +
drivers/cpufreq/rcpufreq_dt.rs | 4 +-
rust/helpers/cpu.c | 8 +++
rust/helpers/helpers.c | 1 +
rust/kernel/cpu.rs | 124 ++++++++++++++++++++++++++++++++-
rust/kernel/cpufreq.rs | 27 ++++---
rust/kernel/cpumask.rs | 51 ++++++++++----
7 files changed, 189 insertions(+), 27 deletions(-)
create mode 100644 rust/helpers/cpu.c
base-commit: 19272b37aa4f83ca52bdf9c16d5d81bdd1354494
prerequisite-patch-id: 1917103231ee798c4217f6da8bafa603b00e554c
--
2.31.1.272.g89b43f80a514
next reply other threads:[~2025-06-10 13:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 13:21 Viresh Kumar [this message]
2025-06-10 13:21 ` [PATCH V3 1/3] rust: cpu: Introduce CpuId abstraction Viresh Kumar
2025-06-11 16:07 ` Boqun Feng
2025-06-10 13:21 ` [PATCH V3 2/3] rust: Use CpuId in place of raw CPU numbers Viresh Kumar
2025-06-11 16:12 ` Boqun Feng
2025-06-12 5:01 ` Viresh Kumar
2025-06-13 15:40 ` Boqun Feng
2025-06-10 13:21 ` [PATCH V3 3/3] rust: cpu: Add CpuId::current() to retrieve current CPU ID Viresh Kumar
2025-06-10 21:23 ` Boqun Feng
2025-06-11 2:28 ` Viresh Kumar
2025-06-10 17:10 ` [PATCH V3 0/3] rust: Introduce CpuId and fix cpumask doctest Miguel Ojeda
2025-06-11 2:18 ` Viresh Kumar
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=cover.1749554685.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tmgross@umich.edu \
--cc=vincent.guittot@linaro.org \
--cc=yury.norov@gmail.com \
/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.