linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: dietmar.eggemann@arm.com (Dietmar Eggemann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] arm: dts: r8a7790: add cpu capacity-dmips-mhz information
Date: Mon, 9 Oct 2017 18:55:07 +0100	[thread overview]
Message-ID: <a0099e02-096c-f8e0-0380-ecb9549f20b4@arm.com> (raw)
In-Reply-To: <20170918073946.GA9156@verge.net.au>

On 18/09/17 08:39, Simon Horman wrote:
> On Wed, Aug 30, 2017 at 03:41:20PM +0100, Dietmar Eggemann wrote:
>> The following 'capacity-dmips-mhz' dt property values are used:
>>
>> Cortex-A15: 1024, Cortex-A7: 539
>>
>> They have been derived form the cpu_efficiency values:
>>
>> Cortex-A15: 3891, Cortex-A7: 2048
>>
>> by scaling them so that the Cortex-A15s (big cores) use 1024.
>>
>> The cpu_efficiency values were originally derived from the "Big.LITTLE
>> Processing with ARM Cortex?-A15 & Cortex-A7" white paper
>> (http://www.cl.cam.ac.uk/~rdm34/big.LITTLE.pdf). Table 1 lists 1.9x
>> (3891/2048) as the Cortex-A15 vs Cortex-A7 performance ratio for the
>> Dhrystone benchmark.
>>
>> The following platform is affected once cpu-invariant accounting
>> support is re-connected to the task scheduler:
> 
> Thanks, applied for v4.15.
> 
> My understanding from the following comment in the cover letter is that not
> currently the case and this there is no behavioural change in applying this
> patch.
> 
> For the record I observed the following with and without this patch
> applied. I believe this is the expected result.
> 
> v4.14-rc1
> # cat /sys/devices/system/cpu/cpu*/cpu_capacity
> 1535
> 1535
> 1535
> 1535
> 1024
> 1024
> 1024
> 1024
> 
> v4.14-rc1 + patch
> # cat /sys/devices/system/cpu/cpu*/cpu_capacity
> 1024
> 1024
> 1024
> 1024
> 539
> 539
> 539
> 539

Thanks Simon! Yes, that is the expected behaviour. And sorry for not
responding earlier!

With exynos542{0,2} and r8a7790 switching to the 'capacity-dmips-mhz'
based solution in v4.15, I can push for removal of the cpu_efficency
code [patch 1/4].

      reply	other threads:[~2017-10-09 17:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-30 14:41 [PATCH 0/4] arm: remove cpu_efficiency Dietmar Eggemann
2017-08-30 14:41 ` [PATCH 1/4] arm: topology: " Dietmar Eggemann
2017-09-04  7:49   ` Vincent Guittot
2017-09-06 11:43     ` Dietmar Eggemann
2017-09-06 12:40       ` Vincent Guittot
2017-09-07 10:41         ` Dietmar Eggemann
2017-08-30 14:41 ` [PATCH 2/4] arm: dts: exynos: add exynos5420 cpu capacity-dmips-mhz information Dietmar Eggemann
2017-08-30 20:26   ` Krzysztof Kozlowski
2017-08-31 10:36     ` Dietmar Eggemann
2017-09-03 19:56       ` Krzysztof Kozlowski
2017-09-06 11:47         ` Dietmar Eggemann
2017-09-17  7:37   ` Krzysztof Kozlowski
2017-08-30 14:41 ` [PATCH 3/4] arm: dts: exynos: add exynos5422 " Dietmar Eggemann
2017-09-17  7:37   ` Krzysztof Kozlowski
2017-08-30 14:41 ` [PATCH 4/4] arm: dts: r8a7790: add " Dietmar Eggemann
2017-09-18  7:39   ` Simon Horman
2017-10-09 17:55     ` Dietmar Eggemann [this message]

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=a0099e02-096c-f8e0-0380-ecb9549f20b4@arm.com \
    --to=dietmar.eggemann@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).