linux-kernel - Re: [PATCH] cpufreq: governors: Reset tunables only for cpufreq_unregister

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] [day] [month] [year] [list]

Message-ID: <CAKohpon8=u2vxNFG0dBJbfpEiu_6kfEQUJyjecw1TxuL6O8WvQ@mail.gmail.com>
Date:	Fri, 1 Feb 2013 11:14:03 +0530
From:	Viresh Kumar <viresh.kumar@...aro.org>
To:	rjw@...k.pl
Cc:	cpufreq@...r.kernel.org, linux-pm@...r.kernel.org,
	linux-kernel@...r.kernel.org, linaro-dev@...ts.linaro.org,
	robin.randhawa@....com, Steve.Bannister@....com,
	Liviu.Dudau@....com, fabio.baltieri@...aro.org,
	Viresh Kumar <viresh.kumar@...aro.org>
Subject: Re: [PATCH] cpufreq: governors: Reset tunables only for cpufreq_unregister_governor()

On 1 February 2013 11:12, Viresh Kumar <viresh.kumar@...aro.org> wrote:
> Currently, whenever governor->governor() is called for CPUFRREQ_GOV_START event
> we reset few tunables of governor. Which isn't correct, as this routine is
> called for every cpu hot-[un]plugging event. We should actually be resetting
> these only when the governor module is removed and re-installed.
>
> Signed-off-by: Viresh Kumar <viresh.kumar@...aro.org>

ARM Mails are broken, please apply attached patch.

Download attachment "0001-cpufreq-governors-Reset-tunables-only-for-cpufreq_un.patch" of type "application/octet-stream" (3955 bytes)