[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170315131657.GI12825@kernel.org>
Date: Wed, 15 Mar 2017 10:16:57 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: Jiri Olsa <jolsa@...hat.com>
Cc: Ravi Bangoria <ravi.bangoria@...ux.vnet.ibm.com>, mingo@...hat.com,
mhiramat@...nel.org, brendan.d.gregg@...il.com,
peterz@...radead.org, alexander.shishkin@...ux.intel.com,
wangnan0@...wei.com, jolsa@...nel.org, ak@...ux.intel.com,
treeze.taeung@...il.com, mathieu.poirier@...aro.org,
hekuang@...wei.com, sukadev@...ux.vnet.ibm.com, ananth@...ibm.com,
naveen.n.rao@...ux.vnet.ibm.com, adrian.hunter@...el.com,
linux-kernel@...r.kernel.org, hemant@...ux.vnet.ibm.com
Subject: Re: [PATCH v5 3/7] perf/sdt: Directly record SDT events with 'perf
record'
Em Wed, Mar 15, 2017 at 01:03:31PM +0100, Jiri Olsa escreveu:
> On Tue, Mar 14, 2017 at 08:36:54PM +0530, Ravi Bangoria wrote:
> > +++ b/tools/perf/builtin-record.c
> > +static int record__parse_events_option(const struct option *opt,
> > + const char *str,
> > + int unset)
> > +{
> > + if (is_sdt_event((char *) str))
> > + return parse_sdt_events_option(opt, str, unset);
> > + else
> > + return parse_events_option(opt, str, unset);
>
> so what happens if there're more than one event in 'str' like:
> -e cycles,std_...
>
> would it be better to plug this directly into parse-events.y
> parser.. and handle it like any other event type?
Yeah, I went to bed thinking about this :-)
Ravi,
Please test something like:
perf record -e cycles,sdt_glib:mem__alloc,sched:*switch -a sleep 5s
- Arnaldo
- Arnaldo
Powered by blists - more mailing lists