From: Lukasz Luba <lukasz.luba@arm.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
dietmar.eggemann@arm.com, rui.zhang@intel.com,
amit.kucheria@verdurent.com, amit.kachhap@gmail.com,
daniel.lezcano@linaro.org, viresh.kumar@linaro.org,
len.brown@intel.com, pavel@ucw.cz, mhiramat@kernel.org,
qyousef@layalina.io, wvw@google.com
Subject: Re: [PATCH v6 02/23] PM: EM: Refactor em_cpufreq_update_efficiencies() arguments
Date: Wed, 10 Jan 2024 13:56:42 +0000 [thread overview]
Message-ID: <453d5cf0-9b74-43ff-bcd4-a6fdd7796056@arm.com> (raw)
In-Reply-To: <CAJZ5v0jCtS1XHczORnZFhwO7N=FommFNbQC7NdaM5SHKXUnTog@mail.gmail.com>
Hi Rafael,
On 1/4/24 19:07, Rafael J. Wysocki wrote:
> The word "refactor" appears to be quite loaded in your patch
> descriptions, but it is not always the best one to use IMV.
Fair enough, I'll change those patches according to your comments.
>
> For instance, this patch simply extends the argument list of
> em_cpufreq_update_efficiencies(), so I would say just that in the
> subject: "Extend em_cpufreq_update_efficiencies() argument list"
>
> On Thu, Jan 4, 2024 at 6:14 PM Lukasz Luba <lukasz.luba@arm.com> wrote:
>>
>> In order to prepare the code for the modifiable EM perf_state table,
>> refactor existing function em_cpufreq_update_efficiencies().
>
> "make em_cpufreq_update_efficiencies() take a pointer to the EM table
> as its second argument and modify it to use that new argument instead
> of the "table" member of dev->em_pd"
>
> or something like this.
I think I got the point, will change it.
>
>> The function now takes the ptr to the EM table as its argument.
>>
>> No functional impact.
>>
>> Signed-off-by: Lukasz Luba <lukasz.luba@arm.com>
>> ---
>> kernel/power/energy_model.c | 8 +++-----
>> 1 file changed, 3 insertions(+), 5 deletions(-)
>>
>> diff --git a/kernel/power/energy_model.c b/kernel/power/energy_model.c
>> index 8b9dd4a39f63..42486674b834 100644
>> --- a/kernel/power/energy_model.c
>> +++ b/kernel/power/energy_model.c
>> @@ -237,10 +237,10 @@ static int em_create_pd(struct device *dev, int nr_states,
>> return 0;
>> }
>>
>> -static void em_cpufreq_update_efficiencies(struct device *dev)
>> +static void
>> +em_cpufreq_update_efficiencies(struct device *dev, struct em_perf_state *table)
>> {
>> struct em_perf_domain *pd = dev->em_pd;
>> - struct em_perf_state *table;
>> struct cpufreq_policy *policy;
>> int found = 0;
>> int i;
>> @@ -254,8 +254,6 @@ static void em_cpufreq_update_efficiencies(struct device *dev)
>> return;
>> }
>>
>> - table = pd->table;
>> -
>> for (i = 0; i < pd->nr_perf_states; i++) {
>> if (!(table[i].flags & EM_PERF_STATE_INEFFICIENT))
>> continue;
>> @@ -397,7 +395,7 @@ int em_dev_register_perf_domain(struct device *dev, unsigned int nr_states,
>>
>> dev->em_pd->flags |= flags;
>>
>> - em_cpufreq_update_efficiencies(dev);
>> + em_cpufreq_update_efficiencies(dev, dev->em_pd->table);
>>
>> em_debug_create_pd(dev);
>> dev_info(dev, "EM: created perf domain\n");
>> --
>
> The code change itself LGTM.
Thanks
next prev parent reply other threads:[~2024-01-10 13:55 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 17:15 [PATCH v6 00/23] Introduce runtime modifiable Energy Model Lukasz Luba
2024-01-04 17:15 ` [PATCH v6 01/23] PM: EM: Add missing newline for the message log Lukasz Luba
2024-01-04 17:15 ` [PATCH v6 02/23] PM: EM: Refactor em_cpufreq_update_efficiencies() arguments Lukasz Luba
2024-01-04 19:07 ` Rafael J. Wysocki
2024-01-10 13:56 ` Lukasz Luba [this message]
2024-01-04 17:15 ` [PATCH v6 03/23] PM: EM: Find first CPU active while updating OPP efficiency Lukasz Luba
2024-01-04 17:15 ` [PATCH v6 04/23] PM: EM: Refactor em_pd_get_efficient_state() to be more flexible Lukasz Luba
2024-01-04 17:15 ` [PATCH v6 05/23] PM: EM: Refactor a new function em_compute_costs() Lukasz Luba
2024-01-04 19:15 ` Rafael J. Wysocki
2024-01-10 13:57 ` Lukasz Luba
2024-01-04 17:15 ` [PATCH v6 06/23] PM: EM: Check if the get_cost() callback is present in em_compute_costs() Lukasz Luba
2024-01-04 17:15 ` [PATCH v6 07/23] PM: EM: Refactor how the EM table is allocated and populated Lukasz Luba
2024-01-04 19:18 ` Rafael J. Wysocki
2024-01-10 13:58 ` Lukasz Luba
2024-01-04 17:15 ` [PATCH v6 08/23] PM: EM: Introduce runtime modifiable table Lukasz Luba
2024-01-04 17:15 ` [PATCH v6 09/23] PM: EM: Use runtime modified EM for CPUs energy estimation in EAS Lukasz Luba
2024-01-04 17:15 ` [PATCH v6 10/23] PM: EM: Add API for memory allocations for new tables Lukasz Luba
2024-01-04 19:35 ` Rafael J. Wysocki
2024-01-10 14:09 ` Lukasz Luba
2024-01-04 17:15 ` [PATCH v6 11/23] PM: EM: Add API for updating the runtime modifiable EM Lukasz Luba
2024-01-04 19:47 ` Rafael J. Wysocki
2024-01-10 14:11 ` Lukasz Luba
2024-01-04 17:15 ` [PATCH v6 12/23] PM: EM: Add helpers to read under RCU lock the EM table Lukasz Luba
2024-01-04 19:55 ` Rafael J. Wysocki
2024-01-10 14:06 ` Lukasz Luba
2024-01-04 17:15 ` [PATCH v6 13/23] PM: EM: Add performance field to struct em_perf_state and optimize Lukasz Luba
2024-01-04 17:15 ` [PATCH v6 14/23] PM: EM: Support late CPUs booting and capacity adjustment Lukasz Luba
2024-01-04 17:15 ` [PATCH v6 15/23] PM: EM: Optimize em_cpu_energy() and remove division Lukasz Luba
2024-01-04 17:15 ` [PATCH v6 16/23] powercap/dtpm_cpu: Use new Energy Model interface to get table Lukasz Luba
2024-01-04 17:15 ` [PATCH v6 17/23] powercap/dtpm_devfreq: " Lukasz Luba
2024-01-04 17:15 ` [PATCH v6 18/23] drivers/thermal/cpufreq_cooling: Use new Energy Model interface Lukasz Luba
2024-01-04 17:15 ` [PATCH v6 19/23] drivers/thermal/devfreq_cooling: " Lukasz Luba
2024-01-04 17:15 ` [PATCH v6 20/23] PM: EM: Change debugfs configuration to use runtime EM table data Lukasz Luba
2024-01-04 17:15 ` [PATCH v6 21/23] PM: EM: Remove old table Lukasz Luba
2024-01-04 17:15 ` [PATCH v6 22/23] PM: EM: Add em_dev_compute_costs() as API for device drivers Lukasz Luba
2024-01-04 17:15 ` [PATCH v6 23/23] Documentation: EM: Update with runtime modification design Lukasz Luba
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=453d5cf0-9b74-43ff-bcd4-a6fdd7796056@arm.com \
--to=lukasz.luba@arm.com \
--cc=amit.kachhap@gmail.com \
--cc=amit.kucheria@verdurent.com \
--cc=daniel.lezcano@linaro.org \
--cc=dietmar.eggemann@arm.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=pavel@ucw.cz \
--cc=qyousef@layalina.io \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=viresh.kumar@linaro.org \
--cc=wvw@google.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®