From: Pierre Gondois <pierre.gondois@arm.com>
To: Lukasz Luba <lukasz.luba@arm.com>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
rafael@kernel.org
Cc: 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, ionela.voinescu@arm.com,
rostedt@goodmis.org, mhiramat@kernel.org
Subject: Re: [PATCH 05/17] trace: energy_model: Add trace event for EM runtime modifications
Date: Tue, 11 Apr 2023 17:39:23 +0200 [thread overview]
Message-ID: <9994acf8-e0bc-55ce-9012-e36ef3b8ddab@arm.com> (raw)
In-Reply-To: <20230314103357.26010-6-lukasz.luba@arm.com>
Hello Lukasz,
Just a suggestion, maybe it would be good to trace the CPUs affected by
the modification. It is possible to retrieve this information by going
to /sys/kernel/debug/energy_model/xxx/cpus, but might be simpler when
parsing a trace.
Regards,
Pierre
On 3/14/23 11:33, Lukasz Luba wrote:
> The Energy Model (EM) supports runtime modifications. Track the changes
> in order to do post-processing analysis. Don't use arrays in the trace
> event, since they are not properly supported by the tools. Instead use
> simple "unroll" with emitting the trace event for each EM array entry
> with proper ID information. The older debugging mechanism which was
> the simple debugfs which dumping the EM content won't be sufficient for
> the modifiable EM purpose. This trace event mechanism would address the
> needs.
>
> Signed-off-by: Lukasz Luba <lukasz.luba@arm.com>
> ---
> include/trace/events/energy_model.h | 46 +++++++++++++++++++++++++++++
> kernel/power/energy_model.c | 3 ++
> 2 files changed, 49 insertions(+)
> create mode 100644 include/trace/events/energy_model.h
>
> diff --git a/include/trace/events/energy_model.h b/include/trace/events/energy_model.h
> new file mode 100644
> index 000000000000..f70babeb5dde
> --- /dev/null
> +++ b/include/trace/events/energy_model.h
> @@ -0,0 +1,46 @@
> +/* SPDX-License-Identifier: GPL-2.0 */
> +#undef TRACE_SYSTEM
> +#define TRACE_SYSTEM energy_model
> +
> +#if !defined(_TRACE_ENERGY_MODEL_H) || defined(TRACE_HEADER_MULTI_READ)
> +#define _TRACE_ENERGY_MODEL_H
> +
> +#include <linux/tracepoint.h>
> +
> +TRACE_EVENT(em_perf_state,
> + TP_PROTO(const char *dev_name, int nr_perf_states, int state,
> + unsigned long ps_frequency, unsigned long ps_power,
> + unsigned long ps_cost, unsigned long ps_flags),
> +
> + TP_ARGS(dev_name, nr_perf_states, state, ps_frequency, ps_power, ps_cost,
> + ps_flags),
> +
> + TP_STRUCT__entry(
> + __string(name, dev_name)
> + __field(int, num_states)
> + __field(int, state)
> + __field(unsigned long, frequency)
> + __field(unsigned long, power)
> + __field(unsigned long, cost)
> + __field(unsigned long, flags)
> + ),
> +
> + TP_fast_assign(
> + __assign_str(name, dev_name);
> + __entry->num_states = nr_perf_states;
> + __entry->state = state;
> + __entry->frequency = ps_frequency;
> + __entry->power = ps_power;
> + __entry->cost = ps_cost;
> + __entry->flags = ps_flags;
> + ),
> +
> + TP_printk("dev_name=%s nr_perf_states=%d state=%d frequency=%lu power=%lu cost=%lu flags=%lu",
> + __get_str(name), __entry->num_states, __entry->state,
> + __entry->frequency, __entry->power, __entry->cost,
> + __entry->flags)
> +);
> +#endif /* _TRACE_ENERGY_MODEL_H */
> +
> +/* This part must be outside protection */
> +#include <trace/define_trace.h>
> diff --git a/kernel/power/energy_model.c b/kernel/power/energy_model.c
> index 937e98a71ed5..3b778743ba89 100644
> --- a/kernel/power/energy_model.c
> +++ b/kernel/power/energy_model.c
> @@ -17,6 +17,9 @@
> #include <linux/sched/topology.h>
> #include <linux/slab.h>
>
> +#define CREATE_TRACE_POINTS
> +#include <trace/events/energy_model.h>
> +
> /*
> * Mutex serializing the registrations of performance domains and letting
> * callbacks defined by drivers sleep.
next prev parent reply other threads:[~2023-04-11 15:39 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 10:33 [PATCH 00/17] Introduce runtime modifiable Energy Model Lukasz Luba
2023-03-14 10:33 ` [PATCH 01/17] PM: EM: Refactor em_cpufreq_update_efficiencies() arguments Lukasz Luba
2023-03-27 17:16 ` Rafael J. Wysocki
2023-04-11 15:43 ` Pierre Gondois
2023-05-10 7:00 ` Lukasz Luba
2023-04-18 22:41 ` Lukasz Luba
2023-03-14 10:33 ` [PATCH 02/17] PM: EM: Find first CPU online while updating OPP efficiency Lukasz Luba
2023-04-11 15:40 ` Pierre Gondois
2023-05-10 7:08 ` Lukasz Luba
2023-05-15 8:47 ` Pierre Gondois
2023-03-14 10:33 ` [PATCH 03/17] PM: EM: Refactor em_pd_get_efficient_state() to be more flexible Lukasz Luba
2023-03-14 10:33 ` [PATCH 04/17] PM: EM: Create a new function em_compute_costs() Lukasz Luba
2023-03-14 10:33 ` [PATCH 05/17] trace: energy_model: Add trace event for EM runtime modifications Lukasz Luba
2023-04-11 15:39 ` Pierre Gondois [this message]
2023-05-10 6:59 ` Lukasz Luba
2023-03-14 10:33 ` [PATCH 06/17] PM: EM: Add update_power() callback for " Lukasz Luba
2023-03-14 10:33 ` [PATCH 07/17] PM: EM: Check if the get_cost() callback is present in em_compute_costs() Lukasz Luba
2023-03-14 10:33 ` [PATCH 08/17] PM: EM: Introduce runtime modifiable table Lukasz Luba
2023-03-14 10:33 ` [PATCH 09/17] PM: EM: Add RCU mechanism which safely cleans the old data Lukasz Luba
2023-03-14 10:33 ` [PATCH 10/17] PM: EM: Add runtime update interface to modify EM power Lukasz Luba
2023-04-11 15:40 ` Pierre Gondois
2023-05-10 6:55 ` Lukasz Luba
2023-05-15 8:48 ` Pierre Gondois
2023-03-14 10:33 ` [PATCH 11/17] PM: EM: Use runtime modified EM for CPUs energy estimation in EAS Lukasz Luba
2023-03-14 10:33 ` [PATCH 12/17] PM: EM: Add argument to get_cost() for runtime modification Lukasz Luba
2023-03-14 10:33 ` [PATCH 13/17] PM: EM: Refactor struct em_perf_domain and add default_table Lukasz Luba
2023-03-15 11:32 ` kernel test robot
2023-03-21 11:30 ` Lukasz Luba
2023-03-14 10:33 ` [PATCH 14/17] Documentation: EM: Add a new section about the design Lukasz Luba
2023-03-14 10:33 ` [PATCH 15/17] Documentation: EM: Add a runtime modifiable EM design description Lukasz Luba
2023-03-14 10:33 ` [PATCH 16/17] Documentation: EM: Add example with driver modifying the EM Lukasz Luba
2023-03-14 10:33 ` [PATCH 17/17] Documentation: EM: Describe the API of runtime modifications 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=9994acf8-e0bc-55ce-9012-e36ef3b8ddab@arm.com \
--to=pierre.gondois@arm.com \
--cc=amit.kachhap@gmail.com \
--cc=amit.kucheria@verdurent.com \
--cc=daniel.lezcano@linaro.org \
--cc=dietmar.eggemann@arm.com \
--cc=ionela.voinescu@arm.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=mhiramat@kernel.org \
--cc=pavel@ucw.cz \
--cc=rafael@kernel.org \
--cc=rostedt@goodmis.org \
--cc=rui.zhang@intel.com \
--cc=viresh.kumar@linaro.org \
/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