From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: David Ahern <dsahern@gmail.com>
Cc: Adrian Hunter <adrian.hunter@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org,
Frederic Weisbecker <fweisbec@gmail.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@gmail.com>,
Paul Mackerras <paulus@samba.org>,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH V3 00/22] perf tools: Introduce an abstraction for Instruction Tracing
Date: Fri, 12 Dec 2014 15:53:24 -0300 [thread overview]
Message-ID: <20141212185324.GF9845@kernel.org> (raw)
In-Reply-To: <548B1425.7090500@gmail.com>
Em Fri, Dec 12, 2014 at 09:13:25AM -0700, David Ahern escreveu:
> On 12/12/14 6:47 AM, Adrian Hunter wrote:
> >Here is V3 of some more preparatory patches for Intel PT
> >that introduce an abstraction for Instruction tracing.
> This is an x86-Intel only feature correct? If that is the case then the code
> should be not compiled for other architectures.
My view so far is that what has been pushed for inclusion facilitates
supporting an event stream that is so huge that needs to be mapped
directly from hardware to tools, that would receive it in a special
area obtained from perf_mmap(). What comes in those events? In this
case, this Intel PT stuff, but noving (should) prevent it from being
used for similar situations for other architectures.
I wonder if we could somehow rename this from 'itrace' to some other
more meaningful name given the above understanding of this being just
a way to directly funnel events from hardware to userspace together with
perf metadata (PERF_RECORD_FORK, PERF_RECORD_MMAP, etc) + other events.
In the kernel this was called a "AUX" thing, which I also think is
vague...
- Arnaldo
next prev parent reply other threads:[~2014-12-12 18:53 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 13:47 [PATCH V3 00/22] perf tools: Introduce an abstraction for Instruction Tracing Adrian Hunter
2014-12-12 13:47 ` [PATCH V3 01/22] perf header: Add Instruction Tracing feature Adrian Hunter
2014-12-12 13:47 ` [PATCH V3 02/22] perf evlist: Add initial support for mmapping an Instruction Trace buffer Adrian Hunter
2014-12-12 13:47 ` [PATCH V3 03/22] perf tools: Add user events for Instruction Tracing Adrian Hunter
2014-12-12 13:47 ` [PATCH V3 04/22] perf tools: Add support for Instruction Trace recording Adrian Hunter
2014-12-12 13:47 ` [PATCH V3 05/22] perf record: Add basic Instruction Tracing support Adrian Hunter
2014-12-12 13:47 ` [PATCH V3 06/22] perf record: Extend -m option for Instruction Tracing mmap pages Adrian Hunter
2014-12-12 13:47 ` [PATCH V3 07/22] perf tools: Add a user event for Instruction Tracing errors Adrian Hunter
2014-12-12 13:47 ` [PATCH V3 08/22] perf session: Add hooks to allow transparent decoding of Instruction Tracing data Adrian Hunter
2014-12-12 13:47 ` [PATCH V3 09/22] perf session: Add Instruction Tracing options Adrian Hunter
2014-12-12 13:47 ` [PATCH V3 10/22] perf itrace: Add helpers for Instruction Tracing errors Adrian Hunter
2014-12-12 13:47 ` [PATCH V3 11/22] perf itrace: Add helpers for queuing Instruction Tracing data Adrian Hunter
2014-12-12 13:47 ` [PATCH V3 12/22] perf itrace: Add a heap for sorting Instruction Tracing queues Adrian Hunter
2014-12-12 13:48 ` [PATCH V3 13/22] perf itrace: Add processing for Instruction Tracing events Adrian Hunter
2014-12-12 13:48 ` [PATCH V3 14/22] perf itrace: Add a hashtable for caching decoded instructions Adrian Hunter
2014-12-12 13:48 ` [PATCH V3 15/22] perf tools: Add member to struct dso for an instruction cache Adrian Hunter
2014-12-12 13:48 ` [PATCH V3 16/22] perf script: Add Instruction Tracing support Adrian Hunter
2014-12-12 13:48 ` [PATCH V3 17/22] perf script: Always allow fields 'addr' and 'cpu' for itrace Adrian Hunter
2014-12-12 13:48 ` [PATCH V3 18/22] perf report: Add Instruction Tracing support Adrian Hunter
2014-12-12 13:48 ` [PATCH V3 19/22] perf inject: Re-pipe Instruction Tracing events Adrian Hunter
2014-12-12 13:48 ` [PATCH V3 20/22] perf inject: Add Instruction Tracing support Adrian Hunter
2014-12-12 13:48 ` [PATCH V3 21/22] perf tools: Add Instruction Tracing index Adrian Hunter
2014-12-12 13:48 ` [PATCH V3 22/22] perf tools: Hit all build ids when Instruction Tracing Adrian Hunter
2014-12-12 16:13 ` [PATCH V3 00/22] perf tools: Introduce an abstraction for " David Ahern
2014-12-12 18:53 ` Arnaldo Carvalho de Melo [this message]
2014-12-15 9:08 ` Adrian Hunter
2014-12-15 15:09 ` David Ahern
2014-12-15 15:13 ` Jiri Olsa
2014-12-15 15:42 ` Arnaldo Carvalho de Melo
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=20141212185324.GF9845@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@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=namhyung@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.