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 12/23] PM: EM: Add helpers to read under RCU lock the EM table
Date: Wed, 10 Jan 2024 14:06:25 +0000 [thread overview]
Message-ID: <429fbf32-f347-4d6a-88dc-362c898c3dfd@arm.com> (raw)
In-Reply-To: <CAJZ5v0g9nEis2Bcvygn70vAT=iifHisZ_7_T4PcmQSU_=_Ymgg@mail.gmail.com>
On 1/4/24 19:55, Rafael J. Wysocki wrote:
> On Thu, Jan 4, 2024 at 6:15 PM Lukasz Luba <lukasz.luba@arm.com> wrote:
>>
>> To use the runtime modifiable EM table there is a need to use RCU
>> read locking properly. Add helper functions for the device drivers and
>> frameworks to make sure it's done properly.
>>
>> Signed-off-by: Lukasz Luba <lukasz.luba@arm.com>
>> ---
>> include/linux/energy_model.h | 19 +++++++++++++++++++
>> 1 file changed, 19 insertions(+)
>>
>> diff --git a/include/linux/energy_model.h b/include/linux/energy_model.h
>> index f33257ed83fd..cfaf5d8b1aad 100644
>> --- a/include/linux/energy_model.h
>> +++ b/include/linux/energy_model.h
>> @@ -338,6 +338,20 @@ static inline int em_pd_nr_perf_states(struct em_perf_domain *pd)
>> return pd->nr_perf_states;
>> }
>>
>> +static inline struct em_perf_state *em_get_table(struct em_perf_domain *pd)
>> +{
>> + struct em_perf_table __rcu *table;
>> +
>> + rcu_read_lock();
>> + table = rcu_dereference(pd->em_table);
>> + return table->state;
>> +}
>> +
>> +static inline void em_put_table(void)
>> +{
>> + rcu_read_unlock();
>> +}
>
> The lack of symmetry between em_get_table() and em_put_table() is kind
> of confusing.
>
> I don't really like these wrappers.
>
> IMO it would be better to use rcu_read_lock()/rcu_read_unlock()
> directly everywhere they are needed and there can be a wrapper around
> rcu_dereference(pd->em_table), something like
>
> static inline struct em_perf_state *em_perf_state_from_pd(struct
> em_perf_domain *pd)
> {
> return rcu_dereference(pd->em_table)->state;
> }
Fair enough, I will change this and use explicit rcu_read_lock/unlock()
in the thermal/DTPM code together with this above function.
I will add comment to it that it needs to be called under the RCU read
section locked.
Then also it would be easier to handle the function names in patch 10/23
that you have also commented.
>
>> +
>> #else
>> struct em_data_callback {};
>> #define EM_ADV_DATA_CB(_active_power_cb, _cost_cb) { }
>> @@ -384,6 +398,11 @@ int em_dev_update_perf_domain(struct device *dev,
>> {
>> return -EINVAL;
>> }
>> +static inline struct em_perf_state *em_get_table(struct em_perf_domain *pd)
>> +{
>> + return NULL;
>> +}
>> +static inline void em_put_table(void) {}
>> #endif
>>
>> #endif
>> --
>
next prev parent reply other threads:[~2024-01-10 14:05 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
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 [this message]
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=429fbf32-f347-4d6a-88dc-362c898c3dfd@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®