From: Javi Merino <javi.merino@arm.com>
To: "Zhang, Rui" <rui.zhang@intel.com>
Cc: Michele DiGiorgio <michele.digiorgio@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Punit Agrawal <punit.agrawal@arm.com>,
Eduardo Valentin <edubezval@gmail.com>
Subject: Re: [PATCH] thermal: trace: migrating thermal traces to use TRACE_DEFINE_ENUM() macros
Date: Tue, 8 Mar 2016 09:58:52 +0000 [thread overview]
Message-ID: <20160308095851.GA3037@e104805> (raw)
In-Reply-To: <744357E9AAD1214791ACBA4B0B9092633A972721@SHSMSX101.ccr.corp.intel.com>
On Tue, Mar 08, 2016 at 09:48:42AM +0000, Zhang, Rui wrote:
> Punit and Javi,
>
> What do you think of this? I'd like to get your ACK before taking it.
Sorry, I didn't realize you were waiting for us. I'm quite happy for
this to go in:
Acked-by: Javi Merino <javi.merino@arm.com>
> > -----Original Message-----
> > From: linux-pm-owner@vger.kernel.org [mailto:linux-pm-
> > owner@vger.kernel.org] On Behalf Of Michele DiGiorgio
> > Sent: Friday, March 04, 2016 1:11 AM
> > To: Steven Rostedt <rostedt@goodmis.org>
> > Cc: linux-pm@vger.kernel.org; Ingo Molnar <mingo@redhat.com>; Javi
> > Merino <javi.merino@arm.com>; linux-kernel@vger.kernel.org; Punit
> > Agrawal <punit.agrawal@arm.com>; Eduardo Valentin <edubezval@gmail.com>
> > Subject: Re: [PATCH] thermal: trace: migrating thermal traces to use
> > TRACE_DEFINE_ENUM() macros
> >
> > Hello Steven,
> >
> > Thanks for acknowledging the patch.
> >
> > Will you be merging it or should I refer to somebody else?
> >
> > Kind regards,
> > Michele
> >
> > On 01/03/16 18:20, Steven Rostedt wrote:
> > > On Tue, 1 Mar 2016 17:38:54 +0000
> > > Michele Di Giorgio <michele.digiorgio@arm.com> wrote:
> > >
> > > > Userspace tools are not aware of how to convert the enums provided
> > > > by the tracepoints to their corresponding strings.
> > > >
> > > > Adding TRACE_DEFINE_ENUM() macros allows to make the enums available
> > > > to userspace to let the tools know what those enum values represent.
> > > >
> > > > In particular, for thermal zone trip types what we obtained before
> > > > was something like:
> > > >
> > > > kworker/1:1-460 [001] 320.372732: thermal_zone_trip:
> > thermal_zone=soc
> > > > id=0 trip=1 trip_type=1
> > > >
> > > > Unfortunately, userspace tools do not know how to convert enum
> > > > values to strings and as a consequence they can only forward the
> > > > enum value to the output. By using TRACE_DEFINE_ENUM() macros for
> > > > thermal traces we get the following trace line:
> > > >
> > > > kworker/1:1-460 [001] 320.372732: thermal_zone_trip:
> > thermal_zone=soc
> > > > id=0 trip=1 trip_type=PASSIVE
> > > >
> > > > Userspace tools are now able to better understand the meaning of the
> > > > trip_type and provide the user with more readable information.
> > > >
> > >
> > > Acked-by: Steven Rostedt <rostedt@goodmis.org>
> > >
> > > -- Steve
> > >
> >
> > IMPORTANT NOTICE: The contents of this email and any attachments are
> > confidential and may also be privileged. If you are not the intended recipient,
> > please notify the sender immediately and do not disclose the contents to any
> > other person, use it for any purpose, or store or copy the information in any
> > medium. Thank you.
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-pm" in the body
> > of a message to majordomo@vger.kernel.org More majordomo info at
> > http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-03-08 9:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 17:38 [PATCH] thermal: trace: migrating thermal traces to use TRACE_DEFINE_ENUM() macros Michele Di Giorgio
2016-03-01 18:20 ` Steven Rostedt
2016-03-03 17:10 ` Michele DiGiorgio
2016-03-03 17:10 ` Michele DiGiorgio
2016-03-03 17:28 ` Steven Rostedt
2016-03-03 17:28 ` Steven Rostedt
2016-03-08 9:48 ` Zhang, Rui
2016-03-08 9:58 ` Javi Merino [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=20160308095851.GA3037@e104805 \
--to=javi.merino@arm.com \
--cc=edubezval@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=michele.digiorgio@arm.com \
--cc=mingo@redhat.com \
--cc=punit.agrawal@arm.com \
--cc=rostedt@goodmis.org \
--cc=rui.zhang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.