From: Steven Rostedt <rostedt@goodmis.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: tom.leiming@gmail.com, stern@rowland.harvard.edu,
linux-pm@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, mingo@redhat.com,
fweisbec@gmail.com, Ming Lei <ming.lei@canonical.com>
Subject: Re: [PATCH v1 1/2] PM/runtime: introduce trace points for tracing rpm_* functions
Date: Tue, 27 Sep 2011 16:31:50 -0400 [thread overview]
Message-ID: <1317155512.26514.36.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <201109272229.23250.rjw@sisk.pl>
On Tue, 2011-09-27 at 22:29 +0200, Rafael J. Wysocki wrote:
> On Tuesday, September 27, 2011, tom.leiming@gmail.com wrote:
> > From: Ming Lei <ming.lei@canonical.com>
> >
> > This patch introduces 3 trace points to prepare for tracing
> > rpm_idle/rpm_suspend/rpm_resume functions, so we can use these
> > trace points to replace the current dev_dbg().
> >
> > Cc: Steven Rostedt rostedt@goodmis.org
> > Signed-off-by: Ming Lei <ming.lei@canonical.com>
>
> I get the following build warning from it:
>
> GEN /home/rafael/src/build/mainline/tosh/Makefile
> CHK include/linux/version.h
> Using /home/rafael/src/linux as source for kernel
> CHK include/generated/utsrelease.h
> CALL /home/rafael/src/linux/scripts/checksyscalls.sh
> CHK include/generated/compile.h
> CC drivers/base/power/runtime.o
> CC kernel/trace/rpm-traces.o
> In file included from /home/rafael/src/linux/include/trace/ftrace.h:296:0,
> from /home/rafael/src/linux/include/trace/define_trace.h:96,
> from /home/rafael/src/linux/include/trace/events/rpm.h:99,
> from /home/rafael/src/linux/kernel/trace/rpm-traces.c:15:
> /home/rafael/src/linux/include/trace/events/rpm.h: In function ‘ftrace_raw_output_rpm_return_int’:
> /home/rafael/src/linux/include/trace/events/rpm.h:76:1: warning: format ‘%p’ expects type ‘void *’, but argument 3 has type ‘long unsigned int’
>
> Care to check?
>
> Rafael
> > +TRACE_EVENT(rpm_return_int,
> > + TP_PROTO(struct device *dev, unsigned long ip, int ret),
> > + TP_ARGS(dev, ip, ret),
> > +
> > + TP_STRUCT__entry(
> > + __string( name, dev_name(dev))
> > + __field( unsigned long, ip )
> > + __field( int, ret )
> > + ),
> > +
> > + TP_fast_assign(
> > + __assign_str(name, dev_name(dev));
> > + __entry->ip = ip;
> > + __entry->ret = ret;
> > + ),
> > +
> > + TP_printk("%pS:%s ret=%d", __entry->ip, __get_str(name),
> > + __entry->ret)
> > +);
> > +
TP_printk("%pS:%s ret=%d", (void *)__entry->ip, __get_str(name),
__entry->ret)
try that.
-- Steve
next prev parent reply other threads:[~2011-09-27 20:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 10:12 tom.leiming
2011-09-27 10:12 ` tom.leiming
2011-09-27 20:06 ` Rafael J. Wysocki
2011-09-27 20:13 ` Steven Rostedt
2011-09-27 20:29 ` Rafael J. Wysocki
2011-09-27 20:31 ` Steven Rostedt [this message]
2011-09-27 20:36 ` Rafael J. Wysocki
2011-09-27 20:43 ` Steven Rostedt
2011-09-27 21:03 ` Rafael J. Wysocki
2011-09-27 10:12 ` [PATCH v1 2/2] PM/runtime: replace dev_dbg with trace_rpm_* tom.leiming
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=1317155512.26514.36.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=ming.lei@canonical.com \
--cc=mingo@redhat.com \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
--cc=tom.leiming@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®