From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Wang Nan <wangnan0@huawei.com>
Cc: Song Liu <songliubraving@fb.com>,
lkml <linux-kernel@vger.kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Kernel Team <Kernel-team@fb.com>
Subject: Re: perf tools: remove option --tail-synthesize ?
Date: Wed, 21 Nov 2018 10:11:56 -0300 [thread overview]
Message-ID: <20181121131156.GG6248@kernel.org> (raw)
In-Reply-To: <89AC26A9-5A18-4608-8889-9C3C9C1C69D3@fb.com>
Em Wed, Nov 21, 2018 at 07:45:28AM +0000, Song Liu escreveu:
> Hi,
>
> I found perf-record --tail-synthesize without --overwrite breaks symbols
> for perf-script, perf-report, etc. For example:
>
> [root@]# ~/perf record -ag --tail-synthesize -- sleep 1
> [ perf record: Woken up 1 times to write data ]
> [ perf record: Captured and wrote 1.129 MB perf.data (3531 samples) ]
> [root@]# ~/perf script | head
> swapper 0 [000] 1250675.051971: 1 cycles:ppp:
> ffffffff81009e15 [unknown] ([unknown])
> ffffffff81196b19 [unknown] ([unknown])
> ffffffff81196579 [unknown] ([unknown])
> ffffffff81110ca7 [unknown] ([unknown])
> ffffffff81a01f4a [unknown] ([unknown])
> ffffffff81a017bf [unknown] ([unknown])
> ffffffff8180e17a [unknown] ([unknown])
>
> perf-record with --overwrite does NOT have this issue.
>
> After digging into this, I found this issue is introduced by commit
> a73e24d240bc136619d382b1268f34d75c9d25ce.
>
> Reverting this commit does fix this issue. However, on a second thought,
> I feel it is probably better just drop --tail-synthesize, as it doesn't
> make much sense without --overwrite. All we need is to do tail_synthesize
> when --overwrite is set.
>
> Thoughts?
Wang, wdyt?
- Arnaldo
next prev parent reply other threads:[~2018-11-21 13:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 7:45 perf tools: remove option --tail-synthesize ? Song Liu
2018-11-21 10:47 ` Jiri Olsa
2018-11-21 17:56 ` Song Liu
2018-11-21 13:11 ` Arnaldo Carvalho de Melo [this message]
2018-11-22 1:50 ` Wangnan (F)
2018-11-22 9:03 ` Jiri Olsa
2018-11-22 18:18 ` Song Liu
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=20181121131156.GG6248@kernel.org \
--to=acme@kernel.org \
--cc=Kernel-team@fb.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=songliubraving@fb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.