linux-kernel - Re: perf tools: Call graph from Intel BTS

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-prev] [day] [month] [year] [list]

Message-ID: <53C0C8A8.6020102@intel.com>
Date:	Sat, 12 Jul 2014 08:33:28 +0300
From:	Adrian Hunter <adrian.hunter@...el.com>
To:	Peter Zijlstra <peterz@...radead.org>
CC:	acme@...nel.org, Jiri Olsa <jolsa@...hat.com>,
	Ingo Molnar <mingo@...nel.org>, linux-kernel@...r.kernel.org,
	Frederic Weisbecker <fweisbec@...il.com>,
	David Ahern <dsahern@...il.com>,
	"Shishkin, Alexander" <alexander.shishkin@...el.com>,
	Paul Mackerras <paulus@...ba.org>,
	Namhyung Kim <namhyung@...nel.org>,
	Stephane Eranian <eranian@...gle.com>
Subject: Re: perf tools: Call graph from Intel BTS

On 11/07/2014 6:36 p.m., Peter Zijlstra wrote:
> On Fri, Jul 11, 2014 at 05:36:41PM +0300, Adrian Hunter wrote:
>> Alexander Shishkin is working on the Intel PT driver for perf
>> and has included a driver for Intel BTS.  I have taken that and
>
> There is already a BTS driver, although I've not used it ever, since
> there's no useful tool for it. One way would be to use that, and migrate
> to PT data later.

Currently that driver does not allow kernel tracing.  Last time I tried it
with that restriction removed, it would lose data on larger workloads.
Generally, any loss of data ruins the call graph.

For me it does not make sense to try to support it, since I am primarily
trying to pave the way for the Intel PT driver.
--
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/