From: Steven Rostedt <rostedt@goodmis.org>
To: Nicolin Chen <nicoleotsuka@gmail.com>
Cc: jdelvare@suse.com, linux@roeck-us.net,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
mingo@redhat.com
Subject: Re: [PATCH] hwmon: (core) Add trace events to _attr_show/store functions
Date: Tue, 9 Oct 2018 15:49:45 -0400 [thread overview]
Message-ID: <20181009154945.65300231@gandalf.local.home> (raw)
In-Reply-To: <20181009191111.GA6166@Asurada-Nvidia.nvidia.com>
On Tue, 9 Oct 2018 12:11:11 -0700
Nicolin Chen <nicoleotsuka@gmail.com> wrote:
> On Tue, Oct 09, 2018 at 02:57:21PM -0400, Steven Rostedt wrote:
>
> > > Trace events are useful for people who collect data from the
> > > ftrace output. This patch adds initial trace events for the
> > > hwmon core. To call hwmon_attr_base() for aligned attr index
> > > numbers, this patch also moves the function upward.
> > >
> > > Ftrace outputs:
> > > ...: hwmon_attr_show_string: index=2, attr_name=in2_label, val=VDD_5V
> > > ...: hwmon_attr_show: index=2, attr_name=in2_input, val=5112
> > > ...: hwmon_attr_show: index=2, attr_name=curr2_input, val=440
> > >
> > > Note that the _attr_show and _attr_store functions are tied
> > > to the _with_info API. So a hwmon driver requiring the trace
> > > events feature should use _with_info API to register a hwmon
> > > device.
> >
> > Hmm, this doesn't really explain why these trace events are needed.
> > They look to be attached to sysfs reads. What's the purpose of tracing
> > these?
>
> Our power folks analyse Ftrace outputs of cpufreq, thermal and
> hwmon (power/voltage/current) so as to get the relationship of
> them. The reason why we specifically need trace events is that
> it's convenient and timestamped, and because both cpufreq and
> thermal already have trace events.
>
> I could add this to make the commit message more convincing if
> you'd prefer that.
I'm not against the patch, but yes, having this in the change log is
helpful.
>
> > > @@ -193,6 +206,7 @@ static ssize_t hwmon_attr_show_string(struct device *dev,
> > > char *buf)
> > > {
> > > struct hwmon_device_attribute *hattr = to_hwmon_attr(devattr);
> > > + enum hwmon_sensor_types type = hattr->type;
> > > const char *s;
> > > int ret;
> > >
> > > @@ -201,6 +215,9 @@ static ssize_t hwmon_attr_show_string(struct device *dev,
> > > if (ret < 0)
> > > return ret;
> > >
> > > + trace_hwmon_attr_show_string(hattr->index + hwmon_attr_base(type),
> >
> > Also, the other to tracepoints use hattr->type, here you create a
> > separate variable. Is that just to keep within the 80 char limit?
>
> Yes. It looks clearer to me than wrapping the line here, since
> complier usually optimize the local variable away.
>
Or you can just break the 80 character limit ;-)
-- Steve
next prev parent reply other threads:[~2018-10-09 19:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 18:26 Nicolin Chen
2018-10-09 18:57 ` Steven Rostedt
2018-10-09 19:11 ` Nicolin Chen
2018-10-09 19:49 ` Steven Rostedt [this message]
2018-10-09 19:57 ` Nicolin Chen
2018-10-09 20:39 ` Guenter Roeck
2018-10-09 20:42 ` Steven Rostedt
2018-10-09 20:52 ` Guenter Roeck
2018-10-09 20:43 ` Steven Rostedt
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=20181009154945.65300231@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mingo@redhat.com \
--cc=nicoleotsuka@gmail.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®