From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Cheng Jian <cj.chengjian@huawei.com>
Cc: Jiri Olsa <jolsa@redhat.com>,
peterz@infradead.org, mingo@redhat.com,
alexander.shishkin@linux.intel.com, namhyung@kernel.org,
xiexiuqi@huawei.com, huawei.libin@huawei.com,
wangnan0@huawei.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] perf/trace : Fix repetitious traces of perf on tracepoint
Date: Wed, 17 Jan 2018 11:25:53 -0300 [thread overview]
Message-ID: <20180117142553.GA13639@kernel.org> (raw)
In-Reply-To: <20180117133342.GH30880@kernel.org>
Em Wed, Jan 17, 2018 at 10:33:42AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Tue, Jan 16, 2018 at 04:06:22PM +0100, Jiri Olsa escreveu:
> > On Tue, Jan 16, 2018 at 08:40:38PM +0800, Cheng Jian wrote:
> > > after this patch, perf script(parent-1040, child-1041):
> > > test_fork 1040 [002] 36.536079: sched:sched_wakeup_new: comm=test_fork pid=1041 prio=120 target_cpu=003
> > > It will match it only once for tracing task(child-1041).
> > > Signed-off-by: Cheng Jian <cj.chengjian@huawei.com>
> > the duplicated events are gone.. solution looks ok to me
> > Reviewed-and-Tested-by: Jiri Olsa <jolsa@kernel.org>
> I noticed that in the past as well, will try to test this too.
Unpatched kernel:
[root@jouet ~]# perf trace --no-syscalls -e sched:sched_wakeup_new time sleep 1
0.000 sched:sched_wakeup_new:time:13571 [120] success=1 CPU:003)
18446744073709.547 sched:sched_wakeup_new:time:13571 [120] success=1 CPU:003)
18446744073709.551 sched:sched_wakeup_new:time:13571 [120] success=1 CPU:003)
18446744073709.551 sched:sched_wakeup_new:time:13571 [120] success=1 CPU:003)
18446744073709.551 sched:sched_wakeup_new:time:13571 [120] success=1 CPU:003)
0.00user 0.00system 0:01.00elapsed 0%CPU (0avgtext+0avgdata 1996maxresident)k
0inputs+0outputs (0major+71minor)pagefaults 0swaps
[root@jouet ~]#
Patched kernel:
[root@seventh ~]# perf trace --no-syscalls -e sched:sched_wakeup_new time sleep 1
0.000 sched:sched_wakeup_new:comm=time pid=339 prio=120 target_cpu=002)
0.001 sched:sched_wakeup_new:comm=time pid=339 prio=120 target_cpu=002)
0.00user 0.00system 0:01.00elapsed 0%CPU (0avgtext+0avgdata 2084maxresident)k
0inputs+0outputs (0major+75minor)pagefaults 0swaps
[root@seventh ~]#
prev parent reply other threads:[~2018-01-17 14:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 12:40 [PATCH v3] perf/trace : Fix repetitious traces of perf on tracepoint Cheng Jian
2018-01-16 14:33 ` Milian Wolff
2018-01-27 9:42 ` chengjian (D)
2018-01-16 15:06 ` Jiri Olsa
2018-01-17 13:33 ` Arnaldo Carvalho de Melo
2018-01-17 14:25 ` Arnaldo Carvalho de Melo [this message]
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=20180117142553.GA13639@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=cj.chengjian@huawei.com \
--cc=huawei.libin@huawei.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=wangnan0@huawei.com \
--cc=xiexiuqi@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