linux-kernel - Re: callchain sampling bug in perf?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 19 Aug 2010 12:04:22 -0300
From:	Arnaldo Carvalho de Melo <acme@...radead.org>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	Frederic Weisbecker <fweisbec@...il.com>,
	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: callchain sampling bug in perf?

Em Thu, Aug 19, 2010 at 04:57:01AM -0400, Christoph Hellwig escreveu:
> On Thu, Aug 19, 2010 at 02:57:22AM +0200, Frederic Weisbecker wrote:
> > Hmm, against which tree are you running? I've just tested callchains
> > record on random kprobe based tracepoint and it seemed to work well
> > on report.
> 
> It's 2.6.36-rc1 + a few filesystem related changes.
> 
> > Could you send me your perf.data and also the resulting archive
> > after the following command: "perf archive" ?
> 
> Both attached.

[acme@...pio tmp]$ tar xvf perf.data.tar.bz2 -C ~/.debug
.build-id/36/4300f12afee3dd5b1a87269d60de586f6b61ce
[kernel.kallsyms]/364300f12afee3dd5b1a87269d60de586f6b61ce
[acme@...pio tmp]$
[acme@...pio tmp]$ cat /home/acme/.perfconfig 
[tui]

	report=off
[acme@...pio tmp]$ perf report
# Events: 11K cycles
#
# Overhead       Command      Shared Object     Symbol
# ........  ............  .................  .........
#
    61.70%        python  [kernel.kallsyms]  [k] xlog_sync
    24.05%     flush-9:1  [kernel.kallsyms]  [k] xlog_sync
     7.99%          sync  [kernel.kallsyms]  [k] xlog_sync
     2.94%  xfssyncd/md1  [kernel.kallsyms]  [k] xlog_sync
     1.54%  compilebench  [kernel.kallsyms]  [k] xlog_sync
     1.31%            sh  [kernel.kallsyms]  [k] xlog_sync
     0.23%         :3500  [kernel.kallsyms]  [k] xlog_sync
     0.17%         :3496  [kernel.kallsyms]  [k] xlog_sync
     0.06%         :3570  [kernel.kallsyms]  [k] xlog_sync
     0.01%         :3590  [kernel.kallsyms]  [k] xlog_sync


#
# (For a higher level overview, try: perf report --sort comm,dso)
#
[acme@...pio tmp]$

# yeah, I need to do what we discussed and make tui activation on the command
# line, this use case proves it, if it needed proving usefulness at all :-)

[acme@...pio tmp]$ cat /home/acme/.perfconfig 
[tui]

	report=on

[acme@...pio tmp]$ perf report

http://vger.kernel.org/~acme/perf/perf-report-tui-callchain-xlog_sync.png

So it seems to work (you tell me if the callchains make sense), and the problem
is just on the stdio based callchain rendering.

Frederic, so it doesn't look like anything in the kernel, just a tools/perf/
problem.

I found some issues on the TUI as well, please press the left key some times
after expanding some callchains, so that the window can be resized, your workload
has just a few top level entries, so the window initially is small, I need to
take into account the (to be expanded) callchains and size it properly.

- Arnaldo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/