[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8fa02b18-7e41-eaea-f054-6842f6e310c6@arm.com>
Date: Wed, 16 Aug 2023 15:05:25 +0200
From: Dietmar Eggemann <dietmar.eggemann@....com>
To: Lukasz Luba <lukasz.luba@....com>, linux-kernel@...r.kernel.org,
linux-pm@...r.kernel.org, rafael@...nel.org
Cc: rui.zhang@...el.com, amit.kucheria@...durent.com,
amit.kachhap@...il.com, daniel.lezcano@...aro.org,
viresh.kumar@...aro.org, len.brown@...el.com, pavel@....cz,
Pierre.Gondois@....com, ionela.voinescu@....com,
mhiramat@...nel.org
Subject: Re: [PATCH v3 08/12] PM: EM: Introduce runtime modifiable table
On 21/07/2023 17:50, Lukasz Luba wrote:
> This patch introduces the new feature: modifiable EM perf_state table.
nit pick: The first sentence doesn't add any information. I would skip it.
[...]
> The runtime modifiable EM data is used by the Energy Aware Scheduler (EAS)
> for the task placement. The EAS is the only user of the 'runtime
> modifiable EM'.
The runtime modifiable EM is currently only used ...
The you can skip the next sentence: "The EAS is the only user ..."
All the other users (thermal, etc.) are still using the
> default (basic) EM. This fact drove the design of this feature.
[...]
Powered by blists - more mailing lists