On Wed, May 20, 2020 at 06:12:28PM -0300, Arnaldo Carvalho de Melo wrote: > Em Sun, May 10, 2020 at 11:06:25PM +0800, Changbin Du escreveu: > > This allows us to trace single thread instead of the whole process. > > I was going to adjust the patch to add, but you forgot to add the entry > to tools/perf/Documentation/perf-ftrace.txt, > > Please do so, > no problem. I will apend a new patch to update all the documentation.
> - Arnaldo > > > Signed-off-by: Changbin Du <[email protected]> > > --- > > tools/perf/builtin-ftrace.c | 2 ++ > > 1 file changed, 2 insertions(+) > > > > diff --git a/tools/perf/builtin-ftrace.c b/tools/perf/builtin-ftrace.c > > index 0b39b6a88026..8d04e5afe2d3 100644 > > --- a/tools/perf/builtin-ftrace.c > > +++ b/tools/perf/builtin-ftrace.c > > @@ -707,6 +707,8 @@ int cmd_ftrace(int argc, const char **argv) > > "List available functions to filter"), > > OPT_STRING('p', "pid", &ftrace.target.pid, "pid", > > "trace on existing process id"), > > + OPT_STRING('t', "tid", &ftrace.target.tid, "tid", > > + "trace on existing thread id (exclusive to --pid)"), > > OPT_INCR('v', "verbose", &verbose, > > "be more verbose"), > > OPT_BOOLEAN('a', "all-cpus", &ftrace.target.system_wide, > > -- > > 2.25.1 > > > > -- > > - Arnaldo -- Cheers, Changbin Du
