From: Danilo Krummrich <dakr@kernel.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
"Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com>,
"Danilo Krummrich" <dakr@redhat.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
linux-pm@vger.kernel.org,
"Vincent Guittot" <vincent.guittot@linaro.org>,
"Stephen Boyd" <sboyd@kernel.org>, "Nishanth Menon" <nm@ti.com>,
rust-for-linux@vger.kernel.org,
"Manos Pitsidianakis" <manos.pitsidianakis@linaro.org>,
"Erik Schilling" <erik.schilling@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Joakim Bech" <joakim.bech@linaro.org>,
"Rob Herring" <robh@kernel.org>,
"Yury Norov" <yury.norov@gmail.com>,
"Burak Emir" <bqe@google.com>,
"Rasmus Villemoes" <linux@rasmusvillemoes.dk>,
"Russell King" <linux@armlinux.org.uk>,
linux-clk@vger.kernel.org,
"Michael Turquette" <mturquette@baylibre.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V9 15/17] rust: cpufreq: Extend abstractions for driver registration
Date: Mon, 14 Apr 2025 11:39:39 +0200 [thread overview]
Message-ID: <Z_zX22N9cFmVpC_5@pollux> (raw)
In-Reply-To: <20250414084706.rjsdaoxmug4p4e7l@vireshk-i7>
On Mon, Apr 14, 2025 at 02:17:06PM +0530, Viresh Kumar wrote:
> On 11-04-25, 13:58, Danilo Krummrich wrote:
> > On Fri, Apr 11, 2025 at 04:25:14PM +0530, Viresh Kumar wrote:
>
> > If no, it seems to me that you can even avoid allocating a struct cpufreq_driver
> > dynamically and make it const instead.
>
> I am not sure if I understood your suggestion. The Registration::new()
> method still updates the instance of cpufreq_driver before passing it
> to the C cpufreq core.
See comment in the diff below.
> diff --git a/rust/kernel/cpufreq.rs b/rust/kernel/cpufreq.rs
> index 4194b9558413..9b275d4d3eb6 100644
> --- a/rust/kernel/cpufreq.rs
> +++ b/rust/kernel/cpufreq.rs
> @@ -685,13 +685,14 @@ fn drop(&mut self) {
> /// Reference: <https://docs.kernel.org/cpu-freq/cpu-drivers.html>
> #[vtable]
> pub trait Driver {
> - /// Driver specific data.
> - ///
> - /// Corresponds to the data retrieved via the kernel's `cpufreq_get_driver_data` function.
> - ///
> - /// Require `Data` to implement `ForeignOwnable`. We guarantee to never move the underlying
> - /// wrapped data structure.
> - type Data: ForeignOwnable;
> + /// Driver's name.
> + const NAME: &'static CStr;
> +
> + /// Driver's flags.
> + const FLAGS: u16;
> +
> + /// Boost support.
> + const BOOST_ENABLED: bool;
>
> /// Policy specific data.
> ///
> @@ -804,8 +805,8 @@ fn register_em(_policy: &mut Policy) {
> ///
> /// ```
> /// use kernel::{
> -/// c_str,
> /// cpu, cpufreq,
> +/// c_str,
> /// device::Device,
> /// macros::vtable,
> /// sync::Arc,
> @@ -817,7 +818,10 @@ fn register_em(_policy: &mut Policy) {
> ///
> /// #[vtable]
> /// impl cpufreq::Driver for FooDriver {
> -/// type Data = ();
> +/// const NAME: &'static CStr = c_str!("cpufreq-foo");
> +/// const FLAGS: u16 = cpufreq::flags::NEED_INITIAL_FREQ_CHECK | cpufreq::flags::IS_COOLING_DEV;
> +/// const BOOST_ENABLED: bool = true;
> +///
> /// type PData = Arc<FooDevice>;
> ///
> /// fn init(policy: &mut cpufreq::Policy) -> Result<Self::PData> {
> @@ -848,13 +852,7 @@ fn register_em(_policy: &mut Policy) {
> /// }
> ///
> /// fn foo_probe(dev: &Device) {
> -/// cpufreq::Registration::<FooDriver>::new_foreign_owned(
> -/// dev,
> -/// c_str!("cpufreq-foo"),
> -/// (),
> -/// cpufreq::flags::NEED_INITIAL_FREQ_CHECK | cpufreq::flags::IS_COOLING_DEV,
> -/// true,
> -/// ).unwrap();
> +/// cpufreq::Registration::<FooDriver>::new_foreign_owned(dev).unwrap();
> /// }
> /// ```
> pub struct Registration<T: Driver> {
You could define Registration<T: Driver> as
pub struct Registration<T: Driver>(
NonNull<bindings::cpufreq_driver>,
PhantomData<T>
);
and subsequently...
> @@ -868,13 +866,12 @@ unsafe impl<T: Driver> Sync for Registration<T> {}
>
> #[allow(clippy::non_send_fields_in_send_ty)]
> // SAFETY: Registration with and unregistration from the cpufreq subsystem can happen from any
> -// thread. Additionally, `T::Data` (which is dropped during unregistration) is `Send`, so it is
> -// okay to move `Registration` to different threads.
> +// thread.
> unsafe impl<T: Driver> Send for Registration<T> {}
>
> impl<T: Driver> Registration<T> {
...add a new const of type bindings::cpufreq_driver, i.e.
const VTABLE: bindings::cpufreq_driver = bindings::cpufreq_driver {
name: Self::copy_name(T::NAME),
boost_enabled: T::BOOST_ENABLED,
flags: T::FLAGS,
[...]
}
const fn copy_name(name: &'static CStr) -> [kernel::ffi::c_char; CPUFREQ_NAME_LEN] {
let src name.as_bytes_with_nul();
let mut dst = [0; CPUFREQ_NAME_LEN];
build_assert!(name.len() <= dst.len());
let mut i = 0;
while i < dst.len() {
dst[i] = src[i];
i += 1;
}
dst
}
You should then be able to store a pointer of Self::VTABLE in your Registration
and and hence avoid dynamic allocation of struct cpufreq_driver.
> /// Registers a CPU frequency driver with the cpufreq core.
> - pub fn new(name: &'static CStr, data: T::Data, flags: u16, boost: bool) -> Result<Self> {
> + pub fn new() -> Result<Self> {
> // Required due to Rust 1.82's stricter handling of `unsafe` in mutable statics. The
> // `unsafe` blocks aren't required anymore with later versions.
> #![allow(unused_unsafe)]
> @@ -886,18 +883,18 @@ pub fn new(name: &'static CStr, data: T::Data, flags: u16, boost: bool) -> Resul
> let drv_ref = drv.get_mut();
>
> // Account for the trailing null byte.
> - let len = name.len() + 1;
> + let len = T::NAME.len() + 1;
> if len > drv_ref.name.len() {
> return Err(EINVAL);
> };
>
> - // SAFETY: `name` is a valid `CStr`, and we are copying it to an array of equal or larger
> - // size.
> - let name = unsafe { &*(name.as_bytes_with_nul() as *const [u8]) };
> + // SAFETY: `T::NAME` is a valid `CStr`, and we are copying it to an array of equal or
> + // larger size.
> + let name = unsafe { &*(T::NAME.as_bytes_with_nul() as *const [u8]) };
> drv_ref.name[..len].copy_from_slice(name);
>
> - drv_ref.boost_enabled = boost;
> - drv_ref.flags = flags;
> + drv_ref.boost_enabled = T::BOOST_ENABLED;
> + drv_ref.flags = T::FLAGS;
>
> // Initialize mandatory callbacks.
> drv_ref.init = Some(Self::init_callback);
> @@ -995,10 +992,6 @@ pub fn new(name: &'static CStr, data: T::Data, flags: u16, boost: bool) -> Resul
> None
> };
>
> - // Set driver data before registering the driver, as the cpufreq core calls few callbacks
> - // before `cpufreq_register_driver` returns.
> - Self::set_data(drv_ref, data)?;
> -
> // SAFETY: It is safe to register the driver with the cpufreq core in the kernel C code.
> to_result(unsafe { bindings::cpufreq_register_driver(drv_ref) })?;
>
> @@ -1012,53 +1005,10 @@ pub fn new(name: &'static CStr, data: T::Data, flags: u16, boost: bool) -> Resul
> ///
> /// Instead the [`Registration`] is owned by [`Devres`] and will be revoked / dropped, once the
> /// device is detached.
> - pub fn new_foreign_owned(
> - dev: &Device,
> - name: &'static CStr,
> - data: T::Data,
> - flags: u16,
> - boost: bool,
> - ) -> Result<()> {
> - Devres::new_foreign_owned(dev, Self::new(name, data, flags, boost)?, GFP_KERNEL)?;
> + pub fn new_foreign_owned(dev: &Device) -> Result<()> {
> + Devres::new_foreign_owned(dev, Self::new()?, GFP_KERNEL)?;
> Ok(())
> }
> -
> - // Sets the `Data` for the CPU frequency driver.
> - fn set_data(drv: &mut bindings::cpufreq_driver, data: T::Data) -> Result<()> {
> - if drv.driver_data.is_null() {
> - // Transfer the ownership of the data to the C code.
> - drv.driver_data = <T::Data as ForeignOwnable>::into_foreign(data) as _;
> - Ok(())
> - } else {
> - Err(EBUSY)
> - }
> - }
> -
> - /// Returns borrowed `Data` previously set for the CPU frequency driver.
> - pub fn data(&mut self) -> Option<<T::Data as ForeignOwnable>::Borrowed<'static>> {
> - let drv = self.drv.get_mut();
> -
> - if drv.driver_data.is_null() {
> - None
> - } else {
> - // SAFETY: The data is earlier set by us from `set_data`.
> - Some(unsafe { <T::Data as ForeignOwnable>::borrow(drv.driver_data) })
> - }
> - }
> -
> - // Clears and returns the `Data` for the CPU frequency driver.
> - fn clear_data(&mut self) -> Option<T::Data> {
> - let drv = self.drv.get_mut();
> -
> - if drv.driver_data.is_null() {
> - None
> - } else {
> - // SAFETY: The data is earlier set by us from `set_data`.
> - let data = Some(unsafe { <T::Data as ForeignOwnable>::from_foreign(drv.driver_data) });
> - drv.driver_data = ptr::null_mut();
> - data
> - }
> - }
> }
>
> // CPU frequency driver callbacks.
> @@ -1313,8 +1263,5 @@ fn drop(&mut self) {
>
> // SAFETY: The driver was earlier registered from `new`.
> unsafe { bindings::cpufreq_unregister_driver(drv) };
> -
> - // Free data
> - drop(self.clear_data());
> }
> }
next prev parent reply other threads:[~2025-04-14 9:39 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 10:54 [PATCH V9 00/17] Rust abstractions for clk, cpumask, cpufreq, OPP Viresh Kumar
2025-04-11 10:55 ` [PATCH V9 01/17] rust: cpumask: Use non-atomic helpers Viresh Kumar
2025-04-11 15:20 ` Yury Norov
2025-04-11 10:55 ` [PATCH V9 02/17] rust: cpumask: Add few more helpers Viresh Kumar
2025-04-11 10:55 ` [PATCH V9 03/17] rust: cpumask: Add initial abstractions Viresh Kumar
2025-04-11 15:54 ` Yury Norov
2025-04-14 11:29 ` Viresh Kumar
2025-04-11 10:55 ` [PATCH V9 04/17] MAINTAINERS: Add entry for Rust cpumask API Viresh Kumar
2025-04-11 10:55 ` [PATCH V9 05/17] rust: clk: Add helpers for Rust code Viresh Kumar
2025-04-11 10:55 ` [PATCH V9 06/17] rust: clk: Add initial abstractions Viresh Kumar
2025-04-11 10:55 ` [PATCH V9 07/17] rust: macros: enable use of hyphens in module names Viresh Kumar
2025-04-11 10:55 ` [PATCH V9 08/17] cpufreq: Use enum for cpufreq flags that use BIT() Viresh Kumar
2025-04-11 16:07 ` Yury Norov
2025-04-11 17:05 ` Miguel Ojeda
2025-04-11 10:55 ` [PATCH V9 09/17] rust: cpu: Add from_cpu() Viresh Kumar
2025-04-11 16:18 ` Yury Norov
2025-04-11 18:03 ` Danilo Krummrich
2025-04-11 10:55 ` [PATCH V9 10/17] rust: opp: Add initial abstractions for OPP framework Viresh Kumar
2025-04-11 10:55 ` [PATCH V9 11/17] rust: opp: Add abstractions for the OPP table Viresh Kumar
2025-04-11 16:29 ` Yury Norov
2025-04-11 10:55 ` [PATCH V9 12/17] rust: opp: Add abstractions for the configuration options Viresh Kumar
2025-04-11 10:55 ` [PATCH V9 13/17] rust: cpufreq: Add initial abstractions for cpufreq framework Viresh Kumar
2025-04-11 10:55 ` [PATCH V9 14/17] rust: cpufreq: Extend abstractions for policy and driver ops Viresh Kumar
2025-04-11 10:55 ` [PATCH V9 15/17] rust: cpufreq: Extend abstractions for driver registration Viresh Kumar
2025-04-11 11:58 ` Danilo Krummrich
2025-04-14 8:47 ` Viresh Kumar
2025-04-14 9:39 ` Danilo Krummrich [this message]
2025-04-14 10:52 ` Viresh Kumar
2025-04-14 11:51 ` Danilo Krummrich
2025-04-11 10:55 ` [PATCH V9 16/17] rust: opp: Extend OPP abstractions with cpufreq support Viresh Kumar
2025-04-11 10:55 ` [PATCH V9 17/17] cpufreq: Add Rust-based cpufreq-dt driver 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=Z_zX22N9cFmVpC_5@pollux \
--to=dakr@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=alex.bennee@linaro.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=bqe@google.com \
--cc=dakr@redhat.com \
--cc=erik.schilling@linaro.org \
--cc=gary@garyguo.net \
--cc=joakim.bech@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linux@rasmusvillemoes.dk \
--cc=manos.pitsidianakis@linaro.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=mturquette@baylibre.com \
--cc=nm@ti.com \
--cc=ojeda@kernel.org \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=tmgross@umich.edu \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@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 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).