| 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
| ||
|
Message-ID: <Z_k-TFCkLWu9eiFt@yury>
Date: Fri, 11 Apr 2025 12:07:40 -0400
From: Yury Norov <yury.norov@...il.com>
To: Viresh Kumar <viresh.kumar@...aro.org>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>,
Miguel Ojeda <miguel.ojeda.sandonis@...il.com>,
Danilo Krummrich <dakr@...hat.com>, Miguel Ojeda <ojeda@...nel.org>,
Alex Gaynor <alex.gaynor@...il.com>,
Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <benno.lossin@...ton.me>,
Andreas Hindborg <a.hindborg@...nel.org>,
Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>,
Danilo Krummrich <dakr@...nel.org>, linux-pm@...r.kernel.org,
Vincent Guittot <vincent.guittot@...aro.org>,
Stephen Boyd <sboyd@...nel.org>, Nishanth Menon <nm@...com>,
rust-for-linux@...r.kernel.org,
Manos Pitsidianakis <manos.pitsidianakis@...aro.org>,
Erik Schilling <erik.schilling@...aro.org>,
Alex Bennée <alex.bennee@...aro.org>,
Joakim Bech <joakim.bech@...aro.org>, Rob Herring <robh@...nel.org>,
Burak Emir <bqe@...gle.com>,
Rasmus Villemoes <linux@...musvillemoes.dk>,
Russell King <linux@...linux.org.uk>, linux-clk@...r.kernel.org,
Michael Turquette <mturquette@...libre.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH V9 08/17] cpufreq: Use enum for cpufreq flags that use
BIT()
On Fri, Apr 11, 2025 at 04:25:07PM +0530, Viresh Kumar wrote:
> The BIT() macro is too complex for Rust's bindgen to interpret as
The BIT() is as simple as '1 << nr'. How that it's so complex for that
tool to realize that '1 << 2' is the constant?
> integer constants. This results in many of the cpufreq macros being
> undefined in Rust auto-generated bindings. By replacing the "#define"
> macros with an "enum", we ensure that bindgen can properly evaluate
> these values, enabling their seamless use in Rust code.
>
> No intentional functional impact.
The code you're wiping is perfectly correct. And you clearly state
that one of your tools is broken. Please fix your tool or find any
other solution.
We don't touch correct code, sorry.
> Suggested-by: Alice Ryhl <aliceryhl@...gle.com>
> Signed-off-by: Viresh Kumar <viresh.kumar@...aro.org>
> ---
> include/linux/cpufreq.h | 96 ++++++++++++++++++++++-------------------
> 1 file changed, 51 insertions(+), 45 deletions(-)
>
> diff --git a/include/linux/cpufreq.h b/include/linux/cpufreq.h
> index 400fee6427a5..354ae35fe708 100644
> --- a/include/linux/cpufreq.h
> +++ b/include/linux/cpufreq.h
> @@ -298,11 +298,12 @@ static inline void cpufreq_stats_record_transition(struct cpufreq_policy *policy
> * CPUFREQ DRIVER INTERFACE *
> *********************************************************************/
>
> -#define CPUFREQ_RELATION_L 0 /* lowest frequency at or above target */
> -#define CPUFREQ_RELATION_H 1 /* highest frequency below or at target */
> -#define CPUFREQ_RELATION_C 2 /* closest frequency to target */
> -/* relation flags */
> -#define CPUFREQ_RELATION_E BIT(2) /* Get if possible an efficient frequency */
> +enum {
> + CPUFREQ_RELATION_L = 0, /* lowest frequency at or above target */
> + CPUFREQ_RELATION_H = BIT(0), /* highest frequency below or at target */
> + CPUFREQ_RELATION_C = BIT(1), /* closest frequency to target */
> + CPUFREQ_RELATION_E = BIT(2), /* Get if possible an efficient frequency */
> +};
>
> #define CPUFREQ_RELATION_LE (CPUFREQ_RELATION_L | CPUFREQ_RELATION_E)
> #define CPUFREQ_RELATION_HE (CPUFREQ_RELATION_H | CPUFREQ_RELATION_E)
> @@ -424,52 +425,57 @@ struct cpufreq_driver {
>
> /* flags */
>
> -/*
> - * Set by drivers that need to update internal upper and lower boundaries along
> - * with the target frequency and so the core and governors should also invoke
> - * the diver if the target frequency does not change, but the policy min or max
> - * may have changed.
> - */
> -#define CPUFREQ_NEED_UPDATE_LIMITS BIT(0)
> +enum {
> + /*
> + * Set by drivers that need to update internal upper and lower
> + * boundaries along with the target frequency and so the core and
> + * governors should also invoke the diver if the target frequency does
> + * not change, but the policy min or max may have changed.
> + */
> + CPUFREQ_NEED_UPDATE_LIMITS = BIT(0),
>
> -/* loops_per_jiffy or other kernel "constants" aren't affected by frequency transitions */
> -#define CPUFREQ_CONST_LOOPS BIT(1)
> + /*
> + * loops_per_jiffy or other kernel "constants" aren't affected by
> + * frequency transitions.
> + */
> + CPUFREQ_CONST_LOOPS = BIT(1),
>
> -/*
> - * Set by drivers that want the core to automatically register the cpufreq
> - * driver as a thermal cooling device.
> - */
> -#define CPUFREQ_IS_COOLING_DEV BIT(2)
> + /*
> + * Set by drivers that want the core to automatically register the
> + * cpufreq driver as a thermal cooling device.
> + */
> + CPUFREQ_IS_COOLING_DEV = BIT(2),
>
> -/*
> - * This should be set by platforms having multiple clock-domains, i.e.
> - * supporting multiple policies. With this sysfs directories of governor would
> - * be created in cpu/cpu<num>/cpufreq/ directory and so they can use the same
> - * governor with different tunables for different clusters.
> - */
> -#define CPUFREQ_HAVE_GOVERNOR_PER_POLICY BIT(3)
> + /*
> + * This should be set by platforms having multiple clock-domains, i.e.
> + * supporting multiple policies. With this sysfs directories of governor
> + * would be created in cpu/cpu<num>/cpufreq/ directory and so they can
> + * use the same governor with different tunables for different clusters.
> + */
> + CPUFREQ_HAVE_GOVERNOR_PER_POLICY = BIT(3),
>
> -/*
> - * Driver will do POSTCHANGE notifications from outside of their ->target()
> - * routine and so must set cpufreq_driver->flags with this flag, so that core
> - * can handle them specially.
> - */
> -#define CPUFREQ_ASYNC_NOTIFICATION BIT(4)
> + /*
> + * Driver will do POSTCHANGE notifications from outside of their
> + * ->target() routine and so must set cpufreq_driver->flags with this
> + * flag, so that core can handle them specially.
> + */
> + CPUFREQ_ASYNC_NOTIFICATION = BIT(4),
>
> -/*
> - * Set by drivers which want cpufreq core to check if CPU is running at a
> - * frequency present in freq-table exposed by the driver. For these drivers if
> - * CPU is found running at an out of table freq, we will try to set it to a freq
> - * from the table. And if that fails, we will stop further boot process by
> - * issuing a BUG_ON().
> - */
> -#define CPUFREQ_NEED_INITIAL_FREQ_CHECK BIT(5)
> + /*
> + * Set by drivers which want cpufreq core to check if CPU is running at
> + * a frequency present in freq-table exposed by the driver. For these
> + * drivers if CPU is found running at an out of table freq, we will try
> + * to set it to a freq from the table. And if that fails, we will stop
> + * further boot process by issuing a BUG_ON().
> + */
> + CPUFREQ_NEED_INITIAL_FREQ_CHECK = BIT(5),
>
> -/*
> - * Set by drivers to disallow use of governors with "dynamic_switching" flag
> - * set.
> - */
> -#define CPUFREQ_NO_AUTO_DYNAMIC_SWITCHING BIT(6)
> + /*
> + * Set by drivers to disallow use of governors with "dynamic_switching"
> + * flag set.
> + */
> + CPUFREQ_NO_AUTO_DYNAMIC_SWITCHING = BIT(6),
> +};
>
> int cpufreq_register_driver(struct cpufreq_driver *driver_data);
> void cpufreq_unregister_driver(struct cpufreq_driver *driver_data);
> --
> 2.31.1.272.g89b43f80a514
Powered by blists - more mailing lists