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]
Date:	Tue, 27 Aug 2013 16:29:52 +0530
From:	Viresh Kumar <viresh.kumar@...aro.org>
To:	Lan Tianyu <lantianyu1986@...il.com>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	Lists linaro-kernel <linaro-kernel@...ts.linaro.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
	"cpufreq@...r.kernel.org" <cpufreq@...r.kernel.org>
Subject: Re: [Query] CPUFreq: Why do we need policy->user_policy?

On 26 August 2013 20:53, Lan Tianyu <lantianyu1986@...il.com> wrote:
> So far as I know, it stores some user's config and cpufreq_update_policy()
> bases on the data in the struct to start a new policy. Cpu thermal driver
> (/driver/thermal/cpu_cooling.c)also will its value to update freq policy
> when receive a cpufreq policy adjust notification.

Yeah, but how are these different from policy->min/max/policy/governor?
Why do we need to replicate this information?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ