From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Sudeep Holla <sudeep.holla@arm.com>,
rjw@rjwysocki.net, lorenzo.pieralisi@arm.com
Cc: leo.yan@linaro.org,
"open list:CPUIDLE DRIVERS" <linux-pm@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2] ARM: cpuidle: Support asymmetric idle definition
Date: Fri, 2 Jun 2017 11:25:16 +0200 [thread overview]
Message-ID: <4fe4558f-5881-11dc-5d36-93c92a272eed@linaro.org> (raw)
In-Reply-To: <3ec88de3-7d18-0ea6-bc27-e98084f2b6f6@arm.com>
On 02/06/2017 11:20, Sudeep Holla wrote:
>
>
> On 01/06/17 12:39, Daniel Lezcano wrote:
>> Some hardware have clusters with different idle states. The current code does
>> not support this and fails as it expects all the idle states to be identical.
>>
>> Because of this, the Mediatek mtk8173 had to create the same idle state for a
>> big.Little system and now the Hisilicon 960 is facing the same situation.
>>
>> Solve this by simply assuming the multiple driver will be needed for all the
>> platforms using the ARM generic cpuidle driver which makes sense because of the
>> different topologies we can support with a single kernel for ARM32 or ARM64.
>>
>> Every CPU has its own driver, so every single CPU can specify in the DT the
>> idle states.
>>
>> This simple approach allows to support the future dynamIQ system, current SMP
>> and HMP.
>>
>> It is unoptimal from a memory point of view for a system with a large number of
>> CPUs but nowadays there is no such system with a cpuidle driver on ARM.
>>
>
> While I agree this may be simple solution, but just not necessary for
> systems with symmetric idle states especially one with large number of
> CPUs. I don't like to see 96 CPU Idle driver on say ThunderX. So we
> *must* have some basic distinction done here.
>
> IMO, we can't punish a large SMP systems just because they don't have
> asymmetric idle states.
Can you point me in the upstream kernel a DTS with 96 cpus and using the
cpuidle-arm driver ?
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2017-06-02 9:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 11:39 Daniel Lezcano
2017-06-02 9:20 ` Sudeep Holla
2017-06-02 9:25 ` Daniel Lezcano [this message]
2017-06-02 9:39 ` Sudeep Holla
2017-06-02 10:06 ` Daniel Lezcano
2017-06-02 10:14 ` Sudeep Holla
2017-06-02 10:40 ` Daniel Lezcano
2017-06-02 13:45 ` Sudeep Holla
2017-06-06 17:28 ` Daniel Lezcano
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=4fe4558f-5881-11dc-5d36-93c92a272eed@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=leo.yan@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=rjw@rjwysocki.net \
--cc=sudeep.holla@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®