[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131216154527.GX22695@tassilo.jf.intel.com>
Date: Mon, 16 Dec 2013 07:45:27 -0800
From: Andi Kleen <ak@...ux.intel.com>
To: Frederic Weisbecker <fweisbec@...il.com>
Cc: Ingo Molnar <mingo@...nel.org>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
David Ahern <dsahern@...il.com>, Jiri Olsa <jolsa@...hat.com>,
Mike Galbraith <efault@....de>,
Namhyung Kim <namhyung@...il.com>,
Paul Mackerras <paulus@...ba.org>,
Stephane Eranian <eranian@...gle.com>,
Adrian Hunter <adrian.hunter@...el.com>
Subject: Re: [PATCH v0 00/71] perf: Add support for Intel Processor Trace
> You're right it's extremely slow. But it can still be relevant for debugging,
> at least for apps that don't do too much CPU bound stuffs.
There are patches from Markus already for gdb to use it (using the old
BTS perf interface). I'm not sure they have been merged into gdb
mainline yet though.
> My hope has always been that we can make a userspace function graph tracer
> out of its dumps. And I think we can, I'm pretty sure that would be a useful tool.
I wrote one, based on the __fentry__, like the kernel:
http://github.com/andikleen/ftracer
BTS has no timing information, so you could at best do a function tracer
without timing.
-Andi
--
ak@...ux.intel.com -- Speaking for myself only
--
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