linux-kernel - Re: Question about FIX ME in cpufreq-dt.c

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

Message-ID: <CAKohpo=k3uTNAak=ejompWe5jW=dTbQS3M2zx=eCwgFJpu_ekw@mail.gmail.com>
Date:	Fri, 21 Nov 2014 09:18:10 +0530
From:	Viresh Kumar <viresh.kumar@...aro.org>
To:	nick <xerofoify@...il.com>
Cc:	"Rafael J. Wysocki" <rjw@...ysocki.net>,
	"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Question about FIX ME in cpufreq-dt.c

On 20 November 2014 22:58, nick <xerofoify@...il.com> wrote:
> Greetings Rafael and the other maintainers,

Hi.

> I am curious about the FIX ME in cpufreq-dt.c about not using a for loop or running this part of the code on all
> CPUs.

In case this isn't enough then the loop should be run for any one CPU
from each cluster.
That will guarantee that we have completed regulator/clk
initialization for all the clusters..
But checking for all CPUs might be fine as well..

> If not can I remove the FIX ME or if it's valid can one of the maintainers send me so advice on to fix it
> as I will write a patch if need be to fix it.

The deal is that we aren't yet sure if we are really required to check
this for all CPUs.
So, we are waiting for the first platform to break and can be fixed
then. So, just leave it
as is for now :)

Thanks for caring for it :)
--
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/