From: Lukasz Luba <lukasz.luba@arm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, sudeep.holla@arm.com,
dietmar.eggemann@arm.com, vincent.guittot@linaro.org,
gregkh@linuxfoundation.org, rafael@kernel.org, mingo@redhat.com
Subject: Re: [PATCH] arch_topology: Trace the update thermal pressure
Date: Thu, 21 Apr 2022 07:26:36 +0100 [thread overview]
Message-ID: <57119511-471e-8700-959b-4094e6bd1a76@arm.com> (raw)
In-Reply-To: <20220420194451.6b9661a0@gandalf.local.home>
On 4/21/22 00:44, Steven Rostedt wrote:
> On Tue, 19 Apr 2022 17:48:01 +0100
> Lukasz Luba <lukasz.luba@arm.com> wrote:
>
>> diff --git a/drivers/base/arch_topology.c b/drivers/base/arch_topology.c
>> index 1d6636ebaac5..4f0392de3081 100644
>> --- a/drivers/base/arch_topology.c
>> +++ b/drivers/base/arch_topology.c
>> @@ -19,6 +19,8 @@
>> #include <linux/rcupdate.h>
>> #include <linux/sched.h>
>>
>> +#include <trace/events/thermal.h>
>> +
>> static DEFINE_PER_CPU(struct scale_freq_data __rcu *, sft_data);
>> static struct cpumask scale_freq_counters_mask;
>> static bool scale_freq_invariant;
>> @@ -195,6 +197,8 @@ void topology_update_thermal_pressure(const struct cpumask *cpus,
>>
>> th_pressure = max_capacity - capacity;
>>
>> + trace_thermal_pressure_update(cpu, th_pressure);
>> +
>> for_each_cpu(cpu, cpus)
>> WRITE_ONCE(per_cpu(thermal_pressure, cpu), th_pressure);
>> }
>> diff --git a/include/trace/events/thermal.h b/include/trace/events/thermal.h
>> index 8a5f04888abd..1bf08ee1a25b 100644
>> --- a/include/trace/events/thermal.h
>> +++ b/include/trace/events/thermal.h
>> @@ -65,6 +65,25 @@ TRACE_EVENT(cdev_update,
>> TP_printk("type=%s target=%lu", __get_str(type), __entry->target)
>> );
>>
>> +TRACE_EVENT(thermal_pressure_update,
>> +
>> + TP_PROTO(int cpu, unsigned long thermal_pressure),
>> +
>> + TP_ARGS(cpu, thermal_pressure),
>> +
>> + TP_STRUCT__entry(
>> + __field(int, cpu)
>> + __field(unsigned long, thermal_pressure)
>
> Note, it is always best to place the bigger object before the smaller one
> (when not properly aligned), as that will help to prevent structure
> "holes". That is:
>
> __field(unsigned long, thermal_pressure)
> __field(int, cpu)
>
>
> Otherwise, you are pretty much guaranteed to have a 4 byte hole between cpu
> and thermal_pressure on 64 bit machines.
>
> Also, for the warning you got from the test robot, if you are using this in
> a module and defining it in the core kernel, you need to add:
>
> EXPORT_TRACEPOINT_SYMBOL_GPL(thermal_pressure_update);
>
> Somewhere in the C file that includes this file and defines
> CREATE_TRACE_POINTS.
>
> -- Steve
>
>
Thank you Steve, I'll swap those fields and add the needed export.
I have to go through those older trace events in that file and
understand if they are correct, since I just followed the pattern
in 'cdev_update'.
Regards,
Lukasz
prev parent reply other threads:[~2022-04-21 6:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 16:48 Lukasz Luba
2022-04-20 8:34 ` kernel test robot
2022-04-25 10:05 ` Lukasz Luba
2022-04-20 23:44 ` Steven Rostedt
2022-04-21 6:26 ` Lukasz Luba [this message]
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=57119511-471e-8700-959b-4094e6bd1a76@arm.com \
--to=lukasz.luba@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rafael@kernel.org \
--cc=rostedt@goodmis.org \
--cc=sudeep.holla@arm.com \
--cc=vincent.guittot@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
all inboxes | Powered by JetHome®