From: Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: mingo@redhat.com, acme@kernel.org, brendan.d.gregg@gmail.com,
peterz@infradead.org, alexander.shishkin@linux.intel.com,
wangnan0@huawei.com, jolsa@kernel.org, ak@linux.intel.com,
treeze.taeung@gmail.com, mathieu.poirier@linaro.org,
hekuang@huawei.com, sukadev@linux.vnet.ibm.com,
ananth@in.ibm.com, naveen.n.rao@linux.vnet.ibm.com,
adrian.hunter@intel.com, linux-kernel@vger.kernel.org,
hemant@linux.vnet.ibm.com,
Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>
Subject: Re: [PATCH v5 3/7] perf/sdt: Directly record SDT events with 'perf record'
Date: Mon, 20 Mar 2017 09:21:58 +0530 [thread overview]
Message-ID: <58CF51DE.5070300@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170317180554.c6b69de1e655eee60e723dbd@kernel.org>
Thanks Masami for detailed review.
Please see my comments below.
On Friday 17 March 2017 02:35 PM, Masami Hiramatsu wrote:
> Hi Ravi,
>
> (I avoided to review parser part since it may go to yacc in next version)
>
> On Tue, 14 Mar 2017 20:36:54 +0530
> Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com> wrote:
>
> [SNIP]
>> @@ -1516,9 +1534,10 @@ static bool dry_run;
>> * using pipes, etc.
>> */
>> static struct option __record_options[] = {
>> - OPT_CALLBACK('e', "event", &record.evlist, "event",
>> - "event selector. use 'perf list' to list available events",
>> - parse_events_option),
>> + OPT_CALLBACK_ARG('e', "event", &record.evlist,
>> + &record.sdt_event_list, "event",
>> + "event selector. use 'perf list' to list available events",
>> + record__parse_events_option),
> Does --event option NOT requires argument without this patch?
> If it should be changed to use OPT_CALLBACK_ARG(), would it be
> better merge this part to previous patch?
Ok. Yes, it does. I think macro name is confusing.
This new macro allows passing of extra data from builtin-*.c to libelf.
One such macro already exists (OPT_CALLBACK_OPTARG), but the
argument is optional for it and thus it ignores the argument. I need
a macro in which argument is necessary and it also allows to pass
extra data. Hence, I introduced this macro.
Will change macro to OPT_CALLBACK_ARGDATA. Please suggest if
you have better name.
> [SNIP]
>> +/*
>> + * Delete the SDT events from uprobe_events file that
>> + * were created initially.
>> + */
>> +void remove_sdt_event_list(struct list_head *sdt_events)
>> +{
>> + struct sdt_event_list *sdt_event;
>> + struct strfilter *filter = NULL;
>> + const char *err = NULL;
>> +
>> + if (list_empty(sdt_events))
>> + return;
>> +
>> + list_for_each_entry(sdt_event, sdt_events, list) {
>> + if (!filter) {
>> + filter = strfilter__new(sdt_event->name, &err);
>> + if (!filter)
>> + goto free_list;
> Don't we need to return error code for this case?
>
>> + } else {
>> + strfilter__or(filter, sdt_event->name, &err);
> strfilter__or() can fail here.
>
>> + }
>> + }
>> +
>> + del_perf_probe_events(filter);
> Here too, if it is ignored silently by design, please comment it here.
Sure. Will think about handling errors in this function.
>
>> +
>> +free_list:
>> + free_sdt_list(sdt_events);
>> +}
>> +
>> +static int get_sdt_events_from_cache(struct perf_probe_event *pev)
>> +{
>> + int ret = 0;
>> +
>> + pev->ntevs = find_cached_events_all(pev, &pev->tevs);
>> +
>> + if (pev->ntevs < 0) {
>> + pr_err("Error: Cache lookup failed (code: %d)\n", pev->ntevs);
>> + ret = pev->ntevs;
>> + } else if (!pev->ntevs) {
>> + pr_err("Error: %s:%s not found in the cache\n",
>> + pev->group, pev->event);
>> + ret = -EINVAL;
>> + } else if (pev->ntevs > 1) {
>> + pr_warning("Warning : Recording on %d occurences of %s:%s\n",
>> + pev->ntevs, pev->group, pev->event);
>> + }
>> +
>> + return ret;
>> +}
>> +
>> +static int add_event_to_sdt_evlist(struct probe_trace_event *tev,
>> + struct list_head *sdt_evlist)
>> +{
>> + struct sdt_event_list *tmp;
> Well, strbuf can make this simpler as below ;-)
>
> struct strbuf buf = STRBUF_INIT;
Sure, will do it.
Thanks :)
Ravi
>> +
>> + tmp = zalloc(sizeof(*tmp));
>> + if (!tmp)
>> + return -ENOMEM;
>> +
>> + INIT_LIST_HEAD(&tmp->list);
> if (strbuf_addf(&buf, "%s:%s", tev->group, tev->event))
> goto error;
>
> tmp->name = strbuf_detach(&buf);
>
>> + list_add(&tmp->list, sdt_evlist);
>> +
>> + return 0;
> error:
> free(tmp);
>
> return -ENOMEM;
>> +}
>> +
>> +static int add_events_to_sdt_evlist(struct perf_probe_event *pev,
>> + struct list_head *sdt_evlist)
>> +{
>> + int i, ret;
>> +
>> + for (i = 0; i < pev->ntevs; i++) {
>> + ret = add_event_to_sdt_evlist(&pev->tevs[i], sdt_evlist);
>> +
>> + if (ret < 0)
>> + return ret;
>> + }
>> + return 0;
>> +}
>
> Thanks,
>
next prev parent reply other threads:[~2017-03-20 3:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 15:06 [PATCH v5 0/7] perf/sdt: Directly record SDT events with 'perf record' Ravi Bangoria
2017-03-14 15:06 ` [PATCH v5 1/7] perf/sdt: Introduce util func is_sdt_event() Ravi Bangoria
2017-03-16 16:34 ` [tip:perf/core] perf probe: " tip-bot for Ravi Bangoria
2017-03-14 15:06 ` [PATCH v5 2/7] perf tool: Add option macro OPT_CALLBACK_ARG Ravi Bangoria
2017-03-14 21:00 ` Arnaldo Carvalho de Melo
2017-03-14 15:06 ` [PATCH v5 3/7] perf/sdt: Directly record SDT events with 'perf record' Ravi Bangoria
2017-03-15 12:03 ` Jiri Olsa
2017-03-15 13:16 ` Arnaldo Carvalho de Melo
2017-03-15 13:49 ` Ravi Bangoria
2017-03-17 9:05 ` Masami Hiramatsu
2017-03-20 3:51 ` Ravi Bangoria [this message]
2017-03-14 15:06 ` [PATCH v5 4/7] perf/sdt: Allow recording of existing events Ravi Bangoria
2017-03-17 23:13 ` Masami Hiramatsu
2017-03-20 9:12 ` Ravi Bangoria
2017-03-21 4:52 ` Masami Hiramatsu
2017-03-14 15:06 ` [PATCH v5 5/7] perf/sdt: Warn when number of events recorded are not equal to cached events Ravi Bangoria
2017-03-14 15:06 ` [PATCH v5 6/7] perf/sdt: List events fetched from uprobe_events Ravi Bangoria
2017-03-14 15:06 ` [PATCH v5 7/7] " Ravi Bangoria
2017-03-17 23:14 ` Masami Hiramatsu
2017-03-20 9:16 ` Ravi Bangoria
2017-03-16 9:51 ` [PATCH v5 0/7] perf/sdt: Directly record SDT events with 'perf record' Masami Hiramatsu
2017-03-16 11:27 ` Ravi Bangoria
2017-03-17 4:42 ` Masami Hiramatsu
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=58CF51DE.5070300@linux.vnet.ibm.com \
--to=ravi.bangoria@linux.vnet.ibm.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=ananth@in.ibm.com \
--cc=brendan.d.gregg@gmail.com \
--cc=hekuang@huawei.com \
--cc=hemant@linux.vnet.ibm.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=sukadev@linux.vnet.ibm.com \
--cc=treeze.taeung@gmail.com \
--cc=wangnan0@huawei.com \
/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;
as well as URLs for NNTP newsgroup(s).