mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Taeung Song <treeze.taeung@gmail.com>
To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
Cc: linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Wang Nan <wangnan0@huawei.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH v2 1/4] perf tools: Create for_each_event macro for tracepoints iteration
Date: Wed, 1 Feb 2017 16:02:22 +0900	[thread overview]
Message-ID: <201871e1-ea5a-baa5-4cbc-abf5002bbc26@gmail.com> (raw)
In-Reply-To: <20170131122116.GA4491@kernel.org>

Hi, Arnaldo :)

On 01/31/2017 09:21 PM, Arnaldo Carvalho de Melo wrote:
> Em Tue, Jan 31, 2017 at 08:38:28PM +0900, Taeung Song escreveu:
>> Such as for_each_subsystem and for_each_event in util/parse-events.c,
>> add new macros 'for_each_event' for easy iteration over the tracepoints
>> in order to be more compact and readable.
>
> Looks ok, applied, but look below for some minor suggestions.
>
> - Arnaldo
>
>> Cc: Steven Rostedt <rostedt@goodmis.org>
>> Cc: Frederic Weisbecker <fweisbec@gmail.com>
>> Cc: Jiri Olsa <jolsa@kernel.org>
>> Cc: Namhyung Kim <namhyung@kernel.org>
>> Signed-off-by: Taeung Song <treeze.taeung@gmail.com>
>> ---
>>  tools/perf/util/trace-event-info.c | 38 ++++++++++++++++++--------------------
>>  1 file changed, 18 insertions(+), 20 deletions(-)
>>
>> diff --git a/tools/perf/util/trace-event-info.c b/tools/perf/util/trace-event-info.c
>> index ceb0e27..fb6d95d 100644
>> --- a/tools/perf/util/trace-event-info.c
>> +++ b/tools/perf/util/trace-event-info.c
>> @@ -170,6 +170,12 @@ static bool name_in_tp_list(char *sys, struct tracepoint_path *tps)
>>  	return false;
>>  }
>>
>> +#define for_each_event(dir, dent, tps)				\
>> +	while ((dent = readdir(dir)))				\
>> +		if (dent->d_type == DT_DIR &&			\
>> +		    (strcmp(dent->d_name, ".")) &&		\
>> +		    (strcmp(dent->d_name, "..")))		\
>> +
>>  static int copy_event_system(const char *sys, struct tracepoint_path *tps)
>>  {
>>  	struct dirent *dent;
>> @@ -186,12 +192,10 @@ static int copy_event_system(const char *sys, struct tracepoint_path *tps)
>>  		return -errno;
>>  	}
>>
>> -	while ((dent = readdir(dir))) {
>> -		if (dent->d_type != DT_DIR ||
>> -		    strcmp(dent->d_name, ".") == 0 ||
>> -		    strcmp(dent->d_name, "..") == 0 ||
>> -		    !name_in_tp_list(dent->d_name, tps))
>> +	for_each_event(dir, dent, tps) {
>> +		if (!name_in_tp_list(dent->d_name, tps))
>>  			continue;
>> +
>>  		if (asprintf(&format, "%s/%s/format", sys, dent->d_name) < 0) {
>>  			err = -ENOMEM;
>>  			goto out;
>> @@ -210,12 +214,10 @@ static int copy_event_system(const char *sys, struct tracepoint_path *tps)
>>  	}
>>
>>  	rewinddir(dir);
>> -	while ((dent = readdir(dir))) {
>> -		if (dent->d_type != DT_DIR ||
>> -		    strcmp(dent->d_name, ".") == 0 ||
>> -		    strcmp(dent->d_name, "..") == 0 ||
>> -		    !name_in_tp_list(dent->d_name, tps))
>> +	for_each_event(dir, dent, tps) {
>> +		if (!name_in_tp_list(dent->d_name, tps))
>>  			continue;
>> +
>>  		if (asprintf(&format, "%s/%s/format", sys, dent->d_name) < 0) {
>>  			err = -ENOMEM;
>>  			goto out;
>> @@ -290,13 +292,11 @@ static int record_event_files(struct tracepoint_path *tps)
>>  		goto out;
>>  	}
>>
>> -	while ((dent = readdir(dir))) {
>> -		if (dent->d_type != DT_DIR ||
>> -		    strcmp(dent->d_name, ".") == 0 ||
>> -		    strcmp(dent->d_name, "..") == 0 ||
>> -		    strcmp(dent->d_name, "ftrace") == 0 ||
>> +	for_each_event(dir, dent, tps) {
>> +		if (!strcmp(dent->d_name, "ftrace") ||
>
> the existing style was == 0, you switched it to !, equivalent, but
> gratuitous, keeping the existing style would make reviewing slightly
> faster, as the pattern wouldn't have changed.
>

I understood !!
In the future, I'll think this when making some patches.

Thanks,
Taeung

  parent reply	other threads:[~2017-02-01  7:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-31 11:38 [PATCH v2 0/4] Add ftrace config and refactor several parts Taeung Song
2017-01-31 11:38 ` [PATCH v2 1/4] perf tools: Create for_each_event macro for tracepoints iteration Taeung Song
2017-01-31 12:21   ` Arnaldo Carvalho de Melo
2017-01-31 12:23     ` Arnaldo Carvalho de Melo
2017-01-31 17:32       ` Steven Rostedt
2017-02-01  7:02     ` Taeung Song [this message]
2017-02-01 14:43   ` [tip:perf/core] " tip-bot for Taeung Song
2017-01-31 11:38 ` [PATCH v2 2/4] perf ftrace: Add ftrace.tracer config option Taeung Song
2017-01-31 12:46   ` Arnaldo Carvalho de Melo
2017-01-31 13:15     ` Arnaldo Carvalho de Melo
2017-02-01  7:27       ` Taeung Song
2017-02-01 14:43   ` [tip:perf/core] " tip-bot for Taeung Song
2017-01-31 11:38 ` [PATCH v2 3/4] perf tools: Check NULL after zalloc() and Use zfree() instead of free() in parse-events.c Taeung Song
2017-01-31 13:23   ` Arnaldo Carvalho de Melo
2017-02-01  8:04     ` Taeung Song
2017-01-31 11:38 ` [PATCH v2 4/4] perf tools: Increase index if perf_evsel__new_idx() succeeded Taeung Song
2017-01-31 13:25   ` Arnaldo Carvalho de Melo
2017-02-01  8:04     ` Taeung Song

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=201871e1-ea5a-baa5-4cbc-abf5002bbc26@gmail.com \
    --to=treeze.taeung@gmail.com \
    --cc=arnaldo.melo@gmail.com \
    --cc=fweisbec@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --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

Powered by JetHome