All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent Guittot <vincent.guittot@linaro.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Amit Kucheria <amit.kucheria@linaro.org>,
	Jean Pihet <jean.pihet@newoldbits.com>,
	linux@arm.linux.org.uk, devicetree-discuss@lists.ozlabs.org,
	linux-kernel@vger.kernel.org, rob.herring@calxeda.com,
	linaro-dev@lists.linaro.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC 3/4] ARM: topology: Update cpu_power according to DT information
Date: Wed, 13 Jun 2012 16:31:19 +0200	[thread overview]
Message-ID: <CAKfTPtAhWrH8M3z-+13iKz4FjNd8LQDJOfOGKcKUx7jLXvtz+g@mail.gmail.com> (raw)
In-Reply-To: <1339594368.8980.41.camel@twins>

On 13 June 2012 15:32, Peter Zijlstra <peterz@infradead.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.


>
>

WARNING: multiple messages have this Message-ID (diff)
From: vincent.guittot@linaro.org (Vincent Guittot)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 3/4] ARM: topology: Update cpu_power according to DT information
Date: Wed, 13 Jun 2012 16:31:19 +0200	[thread overview]
Message-ID: <CAKfTPtAhWrH8M3z-+13iKz4FjNd8LQDJOfOGKcKUx7jLXvtz+g@mail.gmail.com> (raw)
In-Reply-To: <1339594368.8980.41.camel@twins>

On 13 June 2012 15:32, Peter Zijlstra <peterz@infradead.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.


>
>

  reply	other threads:[~2012-06-13 14:31 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-12 12:02 [RFC 0/4] ARM: topology: set the capacity of each cores for big.LITTLE Vincent Guittot
2012-06-12 12:02 ` Vincent Guittot
2012-06-12 12:02 ` [RFC 1/4] ARM: topology: Add arch_scale_freq_power function Vincent Guittot
2012-06-12 12:02   ` Vincent Guittot
2012-06-12 12:02   ` Vincent Guittot
2012-06-13  8:50   ` Jean Pihet
2012-06-13  8:50     ` Jean Pihet
2012-06-13  9:22     ` Vincent Guittot
2012-06-13  9:22       ` Vincent Guittot
2012-06-13 12:52   ` Peter Zijlstra
2012-06-13 12:52     ` Peter Zijlstra
2012-06-13 19:27     ` Andy Whitcroft
2012-06-13 19:27       ` Andy Whitcroft
2012-06-13 19:27       ` Andy Whitcroft
2012-06-13 19:30       ` Joe Perches
2012-06-13 19:30         ` Joe Perches
2012-06-13 21:51       ` Peter Zijlstra
2012-06-13 21:51         ` Peter Zijlstra
2012-06-12 12:02 ` [RFC 2/4] ARM: topology: factorize the update of sibling masks Vincent Guittot
2012-06-12 12:02   ` Vincent Guittot
2012-06-12 12:02   ` Vincent Guittot
2012-06-13 12:54   ` Peter Zijlstra
2012-06-13 12:54     ` Peter Zijlstra
2012-06-12 12:02 ` [RFC 3/4] ARM: topology: Update cpu_power according to DT information Vincent Guittot
2012-06-12 12:02   ` Vincent Guittot
2012-06-12 12:02   ` Vincent Guittot
2012-06-13  8:59   ` Jean Pihet
2012-06-13  8:59     ` Jean Pihet
2012-06-13  9:44     ` Vincent Guittot
2012-06-13  9:44       ` Vincent Guittot
2012-06-13 12:44       ` Amit Kucheria
2012-06-13 12:44         ` Amit Kucheria
2012-06-13 12:47         ` Peter Zijlstra
2012-06-13 12:47           ` Peter Zijlstra
2012-06-13 12:50           ` Jean Pihet
2012-06-13 12:50             ` Jean Pihet
2012-06-13 13:29           ` Vincent Guittot
2012-06-13 13:29             ` Vincent Guittot
2012-06-13 13:32             ` Peter Zijlstra
2012-06-13 13:32               ` Peter Zijlstra
2012-06-13 14:31               ` Vincent Guittot [this message]
2012-06-13 14:31                 ` Vincent Guittot
2012-06-13 13:07   ` Peter Zijlstra
2012-06-13 13:07     ` Peter Zijlstra
2012-06-13 14:54     ` Vincent Guittot
2012-06-13 14:54       ` Vincent Guittot
2012-06-13 16:06       ` Peter Zijlstra
2012-06-13 16:06         ` Peter Zijlstra
2012-06-13 13:09   ` Peter Zijlstra
2012-06-13 13:09     ` Peter Zijlstra
2012-06-13 14:42     ` Nicolas Pitre
2012-06-13 14:42       ` Nicolas Pitre
2012-06-13 13:19   ` Peter Zijlstra
2012-06-13 13:19     ` Peter Zijlstra
2012-06-13 13:19     ` Peter Zijlstra
2012-06-12 12:02 ` [RFC 4/4] sched: cpu_power: enable ARCH_POWER Vincent Guittot
2012-06-12 12:02   ` Vincent Guittot
2012-06-12 12:02   ` Vincent Guittot
2012-06-13 12:50   ` Peter Zijlstra
2012-06-13 12:50     ` Peter Zijlstra
2012-06-13 13:20     ` Vincent Guittot
2012-06-13 13:20       ` Vincent Guittot
2012-06-13 13:20       ` Vincent Guittot
2012-06-13 13:28       ` Peter Zijlstra
2012-06-13 13:28         ` Peter Zijlstra
2012-06-13 13:50         ` Vincent Guittot
2012-06-13 13:50           ` Vincent Guittot
2012-06-20 10:43         ` [tip:sched/core] sched/x86: Remove broken power estimation tip-bot for Peter Zijlstra
2012-07-24 14:13         ` tip-bot for Peter Zijlstra

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAKfTPtAhWrH8M3z-+13iKz4FjNd8LQDJOfOGKcKUx7jLXvtz+g@mail.gmail.com \
    --to=vincent.guittot@linaro.org \
    --cc=amit.kucheria@linaro.org \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=jean.pihet@newoldbits.com \
    --cc=linaro-dev@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=peterz@infradead.org \
    --cc=rob.herring@calxeda.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.