linux-kernel - Re: [PATCH V4 0/2] cpufreq: Sort policy->freq

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:	Fri, 17 Jun 2016 02:56:59 +0200
From:	"Rafael J. Wysocki" <rafael@...nel.org>
To:	Viresh Kumar <viresh.kumar@...aro.org>
Cc:	"Rafael J. Wysocki" <rjw@...ysocki.net>,
	Lists linaro-kernel <linaro-kernel@...ts.linaro.org>,
	"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Steve Muckle <steve.muckle@...aro.org>
Subject: Re: [PATCH V4 0/2] cpufreq: Sort policy->freq_table

On Thu, Jun 16, 2016 at 6:17 PM, Viresh Kumar <viresh.kumar@...aro.org> wrote:
> On 08-06-16, 02:19, Rafael J. Wysocki wrote:
>> On Tuesday, June 07, 2016 03:55:13 PM Viresh Kumar wrote:
>> > Hi Rafael,
>> >
>> > I have spent some more time on this stuff and finally came out with a
>> > very simple solution. I hope you will like it more than the previous
>> > versions.
>> >
>> > Instead of trying to sort the freq-table passed by the drivers, which
>> > was complicated and would have broken some drivers for sure, this patch
>> > just checks if the freq-table is sorted or not.
>> >
>> > If it is sorted, then we just use a different set of helpers for it. The
>> > table can be sorted in both ascending and descending orders now and
>> > helpers are present for both the cases.
>>
>> Well, that's something I was thinking about from the start. :-)
>>
>> > All the patches are pushed here for testing in case anyone wants to try:
>> > git://git.kernel.org/pub/scm/linux/kernel/git/vireshk/pm.git cpufreq/sorted-freq-table
>> >
>> > V3->V4:
>> > - Written from scratch really, completely different approach.
>>
>> I'll look at the code later this week.
>
> Hi Rafael,
>
> Did you get a chance to look at these? Steve may be blocked on this :)

I know, but I have stuff to do other than cpufreq.

And in particular regression fixes take precedence, of course.