[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZ5v0i2O7xLpGrRc5+z=v10En43i7jgz3krm49XaOrtuD0MCQ@mail.gmail.com>
Date: Fri, 5 Feb 2016 04:10:10 +0100
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Viresh Kumar <viresh.kumar@...aro.org>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Linux PM list <linux-pm@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
Juri Lelli <juri.lelli@....com>,
Steve Muckle <steve.muckle@...aro.org>,
Saravana Kannan <skannan@...eaurora.org>
Subject: Re: [PATCH 3/11] cpufreq: governor: Use common global_dbs_data pointer
On Fri, Feb 5, 2016 at 4:02 AM, Viresh Kumar <viresh.kumar@...aro.org> wrote:
> On 04-02-16, 17:52, Rafael J. Wysocki wrote:
>> On Thu, Feb 4, 2016 at 6:36 AM, Viresh Kumar <viresh.kumar@...aro.org> wrote:
>
>> > Consider a two policy system, who is stopping us from setting ondemand
>> > for one of them and conservative for the other one ? And so, we will
>> > have two gdbs_data ..
>>
>> I don't really regard that as an entirely sane thing to do, but you
>> have a point here.
>
> Why? Its quite useful IMO. For example on TC2, we have two clusters of
> A7 and A15. And we actually can configure A7 for interactive and A15
> for ondemand. And this is very useful for performance/power metrics.
Well, doing insane things may give you better results sometimes.
Depending on what you want to achieve and other factors.
Thanks,
Rafael
Powered by blists - more mailing lists