linux-kernel - Re: [PATCH] cpufreq/cppc: changing highest_perf to nominal_perf in cppc_cpufreq_cpu

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20240611094526.vcirawlsdefbkuhf@vireshk-i7>
Date: Tue, 11 Jun 2024 15:15:26 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Ionela Voinescu <ionela.voinescu@....com>
Cc: "liwei (JK)" <liwei728@...wei.com>,
	Beata Michalska <beata.michalska@....com>,
	Vanshidhar Konda <vanshikonda@...amperecomputing.com>,
	rafael@...nel.org, al.stone@...aro.org, ashwin.chaugule@...aro.org,
	linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
	liwei391@...wei.com, liaoyu15@...wei.com
Subject: Re: [PATCH] cpufreq/cppc: changing highest_perf to nominal_perf in
 cppc_cpufreq_cpu_init()

On 11-06-24, 10:39, Ionela Voinescu wrote:
> Makes sense! But maybe we should no longer update policy->cur to the
> current/hardware frequency once a request comes through from a
> governor, and we have a first actually requested value.

Hmm, not sure I understood that. When the request comes from governor,
we only update policy->cur to the requested frequency and not the
actual hardware frequency. And it is very much required. policy->cur
needs to be up to date all the times, it is an important part of the
entire working of the cpufreq core..

-- 
viresh