From: Namhyung Kim <namhyung@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Jiri Olsa <jolsa@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 0/3] tools lib traceevent: Options for plugins
Date: Wed, 23 Apr 2014 15:07:38 +0900 [thread overview]
Message-ID: <87ppk8r32t.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <20140422194824.319892442@goodmis.org> (Steven Rostedt's message of "Tue, 22 Apr 2014 15:48:24 -0400")
Hi Steven,
On Tue, 22 Apr 2014 15:48:24 -0400, Steven Rostedt wrote:
> trace-cmd has a way to set options for plugins, via the command
> line parameter. For example, you can add or remove the parent
> from being printed in function tracing by adding:
>
> -O parent=1
> -O parent=0
>
> This is passed later to the plugin in. But the plugin itself requires
> registering to the application what options it supplies.
>
> This is a three patch series. The first is to set a flag in pevent
> that would prevent plugins from being loaded. This can be supplied
> by the command line as well to produce the old "raw" events.
>
> The second patch adds the infrastructure to let plugins have options.
>
> The third patch adds the options "parent" and "indent" to the
> function plugin. The indent option lets the user print functions
> with or without indenting by their parents.
>
> All that needs to be done now is to add the options to the perf
> command line. Namhyung? ;-)
Well, I'll think about it, maybe next week (or later ;-p)?
Thanks,
Namhyung
prev parent reply other threads:[~2014-04-23 6:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 19:48 [PATCH 0/3] tools lib traceevent: Options for plugins Steven Rostedt
2014-04-22 19:48 ` [PATCH 1/3] tools lib traceevent: Add flag to not load event plugins Steven Rostedt
2014-04-22 19:48 ` [PATCH 2/3] tools lib traceevent: Add options to plugins Steven Rostedt
2014-04-22 19:48 ` [PATCH 3/3] tools lib traceevent: Add options to function plugin Steven Rostedt
2014-04-23 6:07 ` Namhyung Kim [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=87ppk8r32t.fsf@sejong.aot.lge.com \
--to=namhyung@kernel.org \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--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