linux-kernel - Re: [RFC 3/4] ARM: topology: Update cpu

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:	Wed, 13 Jun 2012 16:31:19 +0200
From:	Vincent Guittot <vincent.guittot@...aro.org>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Amit Kucheria <amit.kucheria@...aro.org>,
	Jean Pihet <jean.pihet@...oldbits.com>, linux@....linux.org.uk,
	devicetree-discuss@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
	rob.herring@...xeda.com, linaro-dev@...ts.linaro.org,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [RFC 3/4] ARM: topology: Update cpu_power according to DT information

On 13 June 2012 15:32, Peter Zijlstra <peterz@...radead.org> wrote:
> On Wed, 2012-06-13 at 15:29 +0200, Vincent Guittot wrote:
>> In fact, there is 2 tracks, one for a power aware scheduler and one
>> for setting the capacity of each core of a big.LITTLE system. This
>> patch is for the latter and is not directly link to the power because
>> the default/performance mode of the scheduler should also take
>> advantage of this information
>
> Fair enough.. can you include a little blurp in the changelog on how
> this affects the capacity stuff for big.little and if that works as
> desired due to these patches?

OK, I will add explanations about how this affect the cpu_power field
and the load balance of a big.LITTLE system, what is enhanced with
this modification and what is not.


>
>
--
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/