Linux Power Management development
 help / color / mirror / Atom feed
From: Leo Yan <leo.yan@linaro.org>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
	rjw@rjwysocki.net, lorenzo.pieralisi@arm.com,
	"open list:CPUIDLE DRIVERS" <linux-pm@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: cpuidle: Support asymmetric idle definition
Date: Mon, 22 May 2017 21:34:52 +0800	[thread overview]
Message-ID: <20170522133452.GC9325@leoy-ThinkPad-T440> (raw)
In-Reply-To: <3ce7048e-6d9d-9e46-a6fb-4d3263231536@arm.com>

Hi Sudeep,

On Mon, May 22, 2017 at 02:02:12PM +0100, Sudeep Holla wrote:

[...]

> >>>> On 19/05/17 17:45, 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.
> >>>>>
> >>>>
> >>>> While I agree the we don't support them today, it's better to benchmark
> >>>> and record/compare the gain we get with the support for cluster based
> >>>> idle states.
> >>>
> >>> Sorry, I don't get what you are talking about. What do you want to
> >>> benchmark ? Cluster idling ?
> >>>
> >>
> >> OK, I was not so clear. I had a brief chat with Lorenzo, we have few
> >> reason to have this support:
> >> 1. Different number of states between clusters
> >> 2. Different latencies(this is the one I was referring above, generally
> >>    we keep worst case timings here and wanted to see if any platform
> >>    measured improvements with different latencies in the idle states)
> > 
> > I don't see the point. Are you putting into question the big little design?
> >
> 
> Not exactly. Since they are generally worst case number, I wanted to
> check if someone saw real benefit with 2 different set of values.
> Anyways that's not important or blocking, just raised a point, so that
> we can stick some benchmarking results with this.

In case you are interesting for Hikey960 idle states, you could see
the two clustsers have different idle states:
http://termbin.com/d7ed

[...]

Thanks,
Leo Yan

  reply	other threads:[~2017-05-22 13:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-19 16:45 [PATCH] ARM: cpuidle: Support asymmetric idle definition Daniel Lezcano
2017-05-22 10:11 ` Sudeep Holla
2017-05-22 10:20   ` Daniel Lezcano
2017-05-22 10:32     ` Sudeep Holla
2017-05-22 12:41       ` Daniel Lezcano
2017-05-22 13:02         ` Sudeep Holla
2017-05-22 13:34           ` Leo Yan [this message]
2017-05-22 13:59             ` Sudeep Holla
2017-05-22 14:48           ` Daniel Lezcano
2017-05-22 15:02             ` Sudeep Holla
2017-05-31 16:40               ` Daniel Lezcano
2017-05-31 17:33                 ` Sudeep Holla
2017-06-01  7:37                   ` 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=20170522133452.GC9325@leoy-ThinkPad-T440 \
    --to=leo.yan@linaro.org \
    --cc=daniel.lezcano@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