2013-06-27 (목), 07:51 -0600, David Ahern:
> On 6/26/13 11:04 PM, Namhyung Kim wrote:
> > Hi David,
> >
> > On Wed, 26 Jun 2013 11:10:34 -0600, David Ahern wrote:
> >> On 6/26/13 1:14 AM, Namhyung Kim wrote:
> >>> + const char * const ftrace_usage[] = {
> >>> + "perf ftrace [] []",
> >>> +
On 6/26/13 11:04 PM, Namhyung Kim wrote:
Hi David,
On Wed, 26 Jun 2013 11:10:34 -0600, David Ahern wrote:
On 6/26/13 1:14 AM, Namhyung Kim wrote:
+ const char * const ftrace_usage[] = {
+ "perf ftrace [] []",
+ "perf ftrace [] -- []",
+ NULL
+
Hi David,
On Wed, 26 Jun 2013 11:10:34 -0600, David Ahern wrote:
> On 6/26/13 1:14 AM, Namhyung Kim wrote:
>> +const char * const ftrace_usage[] = {
>> +"perf ftrace [] []",
>> +"perf ftrace [] -- []",
>> +NULL
>> +};
>> +const struct option ftrace_
On 6/26/13 1:14 AM, Namhyung Kim wrote:
+ const char * const ftrace_usage[] = {
+ "perf ftrace [] []",
+ "perf ftrace [] -- []",
+ NULL
+ };
+ const struct option ftrace_options[] = {
+ OPT_STRING('t', "tracer", &ftrace.tracer, "t
From: Namhyung Kim
The ftrace command is a simple wrapper of kernel's ftrace
functionality. It only supports single thread tracing currently and
just reads trace_pipe in text and then write it to stdout.
Cc: Steven Rostedt
Cc: Frederic Weisbecker
Signed-off-by: Namhyung Kim
---
tools/perf/M
5 matches
Mail list logo