linux-kernel - Re: [Query] CPUFreq: Why do we need policy->user

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:	Mon, 26 Aug 2013 23:23:03 +0800
From:	Lan Tianyu <lantianyu1986@...il.com>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	Viresh Kumar <viresh.kumar@...aro.org>,
	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?

2013/8/26 Rafael J. Wysocki <rjw@...k.pl>:
> On Monday, August 26, 2013 08:00:52 PM Viresh Kumar wrote:
>> Hi Rafael,
>
> Hi,
>
>> I am almost done with cleanup of drivers and am back at cpufreq core.. :)
>> I got to this structure: struct cpufreq_real_policy;
>>
>> And I am not able to understand what's the need for this structure?
>> Can you let me know? Before I try to get rid of it :)
>
> Honestly, I don't remember from the top of my head.

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.

>
> Thanks,
> Rafael
>
> --
> To unsubscribe from this list: send the line "unsubscribe cpufreq" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



-- 
Best regards
Tianyu Lan
--
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/