From: Adrian Hunter <adrian.hunter@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: acme@kernel.org, Jiri Olsa <jolsa@redhat.com>,
Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org,
Frederic Weisbecker <fweisbec@gmail.com>,
David Ahern <dsahern@gmail.com>,
"Shishkin, Alexander" <alexander.shishkin@intel.com>,
Paul Mackerras <paulus@samba.org>,
Namhyung Kim <namhyung@kernel.org>,
Stephane Eranian <eranian@google.com>
Subject: Re: perf tools: Call graph from Intel BTS
Date: Sat, 12 Jul 2014 08:33:28 +0300 [thread overview]
Message-ID: <53C0C8A8.6020102@intel.com> (raw)
In-Reply-To: <20140711153626.GP20603@laptop.programming.kicks-ass.net>
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.
prev parent reply other threads:[~2014-07-12 5:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 14:36 perf tools: Call graph from Intel BTS Adrian Hunter
2014-07-11 15:18 ` Arnaldo Carvalho de Melo
2014-07-12 5:33 ` Adrian Hunter
2014-07-11 15:36 ` Peter Zijlstra
2014-07-12 5:33 ` Adrian Hunter [this message]
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=53C0C8A8.6020102@intel.com \
--to=adrian.hunter@intel.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@intel.com \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).