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

Message-ID: <CAKohpokJzEMKuupBunzBSQTRJ-4D=xeLHyyH3C9E1tSLJuJBwg@mail.gmail.com>
Date:	Wed, 28 Aug 2013 11:12:54 +0530
From:	Viresh Kumar <viresh.kumar@...aro.org>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	Lan Tianyu <lantianyu1986@...il.com>,
	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 28 August 2013 02:50, Rafael J. Wysocki <rjw@...k.pl> wrote:
> On Tuesday, August 27, 2013 10:04:52 PM Lan Tianyu wrote:

>> From my understanding.policy->min/max may be modified by some drivers
>> but the user_policy only store user space config and should not be changed
>> by other reason.  :)
>
> Yes, that was the original idea IIRC, so separate user settings from stuff that
> may be changed internally by the kernel.

Yeah, that's what I understood too now.. Anyway I am going to do some core
cleanups now, drivers are mostly done and will see if something can be done
to get rid of them... Otherwise will keep them as is.
--
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/