[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231214053653.hnyeormwu42un5sc@vireshk-i7>
Date: Thu, 14 Dec 2023 11:06:53 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Tim Chen <tim.c.chen@...ux.intel.com>
Cc: Vincent Guittot <vincent.guittot@...aro.org>,
catalin.marinas@....com, will@...nel.org, sudeep.holla@....com,
rafael@...nel.org, agross@...nel.org, andersson@...nel.org,
konrad.dybcio@...aro.org, mingo@...hat.com, peterz@...radead.org,
juri.lelli@...hat.com, dietmar.eggemann@....com,
rostedt@...dmis.org, bsegall@...gle.com, mgorman@...e.de,
bristot@...hat.com, vschneid@...hat.com, lukasz.luba@....com,
rui.zhang@...el.com, mhiramat@...nel.org,
daniel.lezcano@...aro.org, amit.kachhap@...il.com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-pm@...r.kernel.org, linux-arm-msm@...r.kernel.org,
linux-trace-kernel@...r.kernel.org
Subject: Re: [PATCH 1/4] cpufreq: Add a cpufreq pressure feedback for the
scheduler
On 13-12-23, 16:41, Tim Chen wrote:
> Seems like the pressure value computed from the first CPU applies to all CPU.
> Will this be valid for non-homogeneous CPUs that could have different
> max_freq and max_capacity?
The will be part of different cpufreq policies and so it will work
fine.
--
viresh
Powered by blists - more mailing lists