linux-kernel - Re: [PATCH] cpufreq: Add debug print for current frequency in __cpufreq_driver

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 for Android: free password hash cracker in your pocket

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

Message-ID: <ezppyby2fs2k2njwcty4dpaf4637g24kzmemjm5sedeerl6ihw@brxxfglbitxc>
Date: Fri, 30 Jan 2026 11:57:47 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Pengjie Zhang <zhangpengjie2@...wei.com>
Cc: rafael@...nel.org, linux-pm@...r.kernel.org, 
	linux-kernel@...r.kernel.org, zhanjie9@...ilicon.com, zhenglifeng1@...wei.com, 
	lihuisong@...wei.com, yubowen8@...wei.com, linhongye@...artners.com, 
	linuxarm@...wei.com, jonathan.cameron@...wei.com, wangzhi12@...wei.com
Subject: Re: [PATCH] cpufreq: Add debug print for current frequency in
 __cpufreq_driver_target()

On 29-01-26, 20:18, Pengjie Zhang wrote:
> Include policy->cur in the debug message to explicitly show the frequency
> transition (from current to target).
> 
> Signed-off-by: Pengjie Zhang <zhangpengjie2@...wei.com>
> ---
>  drivers/cpufreq/cpufreq.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
> index 4472bb1ec83c..b3d2d2e0c864 100644
> --- a/drivers/cpufreq/cpufreq.c
> +++ b/drivers/cpufreq/cpufreq.c
> @@ -2361,8 +2361,8 @@ int __cpufreq_driver_target(struct cpufreq_policy *policy,
>  	target_freq = __resolve_freq(policy, target_freq, policy->min,
>  				     policy->max, relation);
>  
> -	pr_debug("target for CPU %u: %u kHz, relation %u, requested %u kHz\n",
> -		 policy->cpu, target_freq, relation, old_target_freq);
> +	pr_debug("CPU %u: cur %u kHz -> target %u kHz (req %u kHz, rel %u)\n",
> +		policy->cpu, policy->cur, target_freq, old_target_freq, relation);
>  
>  	/*
>  	 * This might look like a redundant call as we are checking it again

Acked-by: Viresh Kumar <viresh.kumar@...aro.org>

-- 
viresh