From: Tom Zanussi <tom.zanussi@linux.intel.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: masami.hiramatsu.pt@hitachi.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 02/10] tracing: add basic event trigger framework
Date: Tue, 27 Aug 2013 14:36:54 -0500 [thread overview]
Message-ID: <1377632214.15688.38.camel@empanada> (raw)
In-Reply-To: <20130827151257.49e23316@gandalf.local.home>
On Tue, 2013-08-27 at 15:12 -0400, Steven Rostedt wrote:
> On Mon, 26 Aug 2013 22:55:59 -0500
> Tom Zanussi <tom.zanussi@linux.intel.com> wrote:
>
>
> > diff --git a/kernel/trace/trace.h b/kernel/trace/trace.h
> > index b1227b9..1733ac9 100644
> > --- a/kernel/trace/trace.h
> > +++ b/kernel/trace/trace.h
> > @@ -1016,9 +1016,184 @@ extern void trace_event_enable_cmd_record(bool enable);
> > extern int event_trace_add_tracer(struct dentry *parent, struct trace_array *tr);
> > extern int event_trace_del_tracer(struct trace_array *tr);
> >
> > +extern struct ftrace_event_file *find_event_file(struct trace_array *tr,
> > + const char *system,
> > + const char *event);
>
> This patch breaks bisection as you need to remove the static from
> find_event_file() too.
>
> Also, it adds a lot of warnings like "register_event_command" defined
> but not used.
>
> My scripts will fail this patch if it adds a warning. No static
> function should be added without being used.
>
Oops, sorry about that - I accidentally posted the v6 branch (though the
URL correctly pointed to v7).
The v7 branch actually fixes those problems, which I'll repost now..
Tom
> -- Steve
>
> > +
> > +static inline void *event_file_data(struct file *filp)
> > +{
> > + return ACCESS_ONCE(file_inode(filp)->i_private);
> > +}
> > +
> > extern struct mutex event_mutex;
> > extern struct list_head ftrace_events;
> >
next prev parent reply other threads:[~2013-08-27 19:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 3:55 [PATCH v7 00/10] tracing: trace event triggers Tom Zanussi
2013-08-27 3:55 ` [PATCH v7 01/10] tracing: Add support for SOFT_DISABLE to syscall events Tom Zanussi
2013-08-27 3:55 ` [PATCH v7 02/10] tracing: add basic event trigger framework Tom Zanussi
2013-08-27 19:12 ` Steven Rostedt
2013-08-27 19:36 ` Tom Zanussi [this message]
2013-08-27 3:56 ` [PATCH v7 03/10] tracing: add 'traceon' and 'traceoff' event trigger commands Tom Zanussi
2013-08-27 3:56 ` [PATCH v7 04/10] tracing: add 'snapshot' event trigger command Tom Zanussi
2013-08-27 3:56 ` [PATCH v7 05/10] tracing: add 'stacktrace' " Tom Zanussi
2013-08-27 3:56 ` [PATCH v7 06/10] tracing: add 'enable_event' and 'disable_event' event trigger commands Tom Zanussi
2013-08-27 3:56 ` [PATCH v7 07/10] tracing: add and use generic set_trigger_filter() implementation Tom Zanussi
2013-08-27 3:56 ` [PATCH v7 08/10] tracing: update event filters for multibuffer Tom Zanussi
2013-08-27 3:56 ` [PATCH v7 09/10] tracing: add documentation for trace event triggers Tom Zanussi
2013-08-27 3:56 ` [PATCH v7 10/10] tracing: make register/unregister_ftrace_command __init Tom Zanussi
2013-08-27 11:35 ` [PATCH v7 00/10] tracing: trace event triggers Masami Hiramatsu
2013-08-27 13:07 ` Steven Rostedt
2013-08-27 14:16 ` Tom Zanussi
2013-08-27 19:40 [PATCH v7 00/10] tracing: trace event triggers (repost) Tom Zanussi
2013-08-27 19:40 ` [PATCH v7 02/10] tracing: add basic event trigger framework Tom Zanussi
2013-08-27 20:15 ` Steven Rostedt
2013-08-27 23:38 ` Tom Zanussi
2013-08-27 20:17 ` 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=1377632214.15688.38.camel@empanada \
--to=tom.zanussi@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=rostedt@goodmis.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
Powered by JetHome