public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Naohiro Aota <naota@elisp.net>,
	Peter Zijlstra <peterz@infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	David Ahern <dsahern@gmail.com>,
	namhyung@kernel.org, Jiri Olsa <jolsa@redhat.com>,
	Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH perf/core  1/4] [BUGFIX] perf probe: List probes in stdout
Date: Sat, 13 Jun 2015 10:14:50 +0900	[thread overview]
Message-ID: <557B840A.4040802@hitachi.com> (raw)
In-Reply-To: <20150612191200.GB6850@kernel.org>

On 2015/06/13 4:12, Arnaldo Carvalho de Melo wrote:
> Em Fri, Jun 12, 2015 at 02:08:13PM +0900, Masami Hiramatsu escreveu:
>> Since commit 5e17b28f1e24 ("perf probe: Add --quiet option to
>> suppress output result message") have replaced printf with pr_info,
>> perf probe -l outputs its result in stderr. However, that is not
>> what the commit expected.
>> e.g.
>>   -----
>>   # perf probe -l > /dev/null
>>     probe:vfs_read       (on vfs_read@ksrc/linux-3/fs/read_write.c)
>>   -----
>> With this fix,
>>   -----
>>   # perf probe -l > list
>>   # cat list
>>     probe:vfs_read       (on vfs_read@ksrc/linux-3/fs/read_write.c)
> 
> Nope, with this fix just applied:

Oops, I missed to rewrite...

[...]
>> @@ -2200,9 +2220,10 @@ static int __show_perf_probe_events(int fd, bool is_kprobe,
>>  				goto next;
>>  			ret = convert_to_perf_probe_event(&tev, &pev,
>>  								is_kprobe);
>> -			if (ret >= 0)
>> -				ret = show_perf_probe_event(&pev,
>> -							    tev.point.module);
>> +			if (ret < 0)
>> +				goto next;
>> +			ret = show_perf_probe_event(&pev, tev.point.module,
>> +						    false);
>>  		}
>>  next:
>>  		clear_perf_probe_event(&pev);
>> @@ -2463,7 +2484,7 @@ static int __add_probe_trace_events(struct perf_probe_event *pev,
>>  		group = pev->group;
>>  		pev->event = tev->event;
>>  		pev->group = tev->group;
>> -		show_perf_probe_event(pev, tev->point.module);
>> +		show_perf_probe_event(pev, tev->point.module, true);
>>  		/* Trick here - restore current event/group */
>>  		pev->event = (char *)event;
>>  		pev->group = (char *)group;
>>
> 

These true/false are opposite!


-- 
Masami HIRAMATSU
Linux Technology Research Center, System Productivity Research Dept.
Center for Technology Innovation - Systems Engineering
Hitachi, Ltd., Research & Development Group
E-mail: masami.hiramatsu.pt@hitachi.com

  reply	other threads:[~2015-06-13  1:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-12  5:08 [PATCH perf/core 0/4] perf-probe bugfixes Masami Hiramatsu
2015-06-12  5:08 ` [PATCH perf/core 1/4] [BUGFIX] perf probe: List probes in stdout Masami Hiramatsu
2015-06-12 19:12   ` Arnaldo Carvalho de Melo
2015-06-13  1:14     ` Masami Hiramatsu [this message]
2015-06-12  5:08 ` [PATCH perf/core 2/4] [BUGFIX] perf probe: Cut off the postfixes from event name Masami Hiramatsu
2015-06-12 19:16   ` Arnaldo Carvalho de Melo
2015-06-18  8:12   ` [tip:perf/core] perf probe: Cut off the gcc optimization postfixes from function name tip-bot for Masami Hiramatsu
2015-06-12  5:08 ` [PATCH perf/core 3/4] [BUGFIX] perf probe: Check non-probe-able symbols when using symbol map Masami Hiramatsu
2015-06-12 19:17   ` Arnaldo Carvalho de Melo
2015-06-13  1:16     ` Masami Hiramatsu
2015-06-12  5:08 ` [PATCH perf/core 4/4] [BUGFIX] perf probe: Show usage even if the last event is skipped Masami Hiramatsu
2015-06-12 19:29 ` [PATCH perf/core 0/4] perf-probe bugfixes Arnaldo Carvalho de Melo

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=557B840A.4040802@hitachi.com \
    --to=masami.hiramatsu.pt@hitachi.com \
    --cc=acme@kernel.org \
    --cc=dsahern@gmail.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=naota@elisp.net \
    --cc=peterz@infradead.org \
    /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