[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090705085949.GA23780@elte.hu>
Date: Sun, 5 Jul 2009 10:59:49 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Frederic Weisbecker <fweisbec@...il.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Mike Galbraith <efault@....de>,
Paul Mackerras <paulus@...ba.org>,
Anton Blanchard <anton@...ba.org>,
Jens Axboe <jens.axboe@...cle.com>,
Arnaldo Carvalho de Melo <acme@...hat.com>
Subject: Re: [PATCH 5/5] perf report: Support callchains with relative
overhead rate
btw., i get some buggy looking output with:
$ perf record -f -g ~/hackbench 10
$ perf report -c
|--5.11%-- unix_stream_sendmsg
| |
| |--100.00%-- __sock_sendmsg
| | sock_aio_write
| | do_sync_write
| | vfs_write
| | sys_write
| | sysenter_dispatch
| | 0xf7f72430
| | 0xffebbca000000014
| |
| --11.11%-- sock_aio_write
| do_sync_write
| vfs_write
| sys_write
| sysenter_dispatch
| 0xf7f72430
| 0xffebbca000000014
Those percentages dont sum up to 100% :-)
Another detail: i think we should signal when we crop the output due
to the filter, via a line of:
| [...]
or so.
Plus, when doing 'perf report' on a call-chain recording, shouldnt
we auto-detect this fact and default to fractal output
automatically, instead of flat mode?
User can still force flat mode via 'perf report -c flat'.
Ingo
--
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/
Powered by blists - more mailing lists