From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, David Ahern <dsahern@gmail.com>,
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>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
"Kleen, Andi" <andi.kleen@intel.com>
Subject: Re: [PATCH V5 00/25] perf tools: Introduce an abstraction for Instruction Tracing
Date: Thu, 12 Mar 2015 17:57:25 -0300 [thread overview]
Message-ID: <20150312205725.GJ3550@kernel.org> (raw)
In-Reply-To: <5501FC45.4060901@intel.com>
Em Thu, Mar 12, 2015 at 10:51:17PM +0200, Adrian Hunter escreveu:
> On 11/03/2015 9:33 p.m., Arnaldo Carvalho de Melo wrote:
> >We'll get that sorted out eventually. Sorry for the flux, but its trying
> >to get it to a better, more fine grained state.
> >>I will send another revision of the patch set, but I am also
> >>considered renaming everything from "itrace" to something more
> >>generic. Possibly "auxtrace" or "hwtrace". Any preferences?
> >That should match whatever name is used for the kernel facility it will
> >handle.... both auxtrace and hwtrace looks too ambiguous...
> >cputrace perhaps?
> "cputrace" sounds a bit like what perf already does. I am leaning toward
> "auxtrace" which got Andi's vote.
> It is possible Peter is waiting on perf tools patches before
> moving the kernel driver patches. Are you amenable to taking
> more of my patches or are you waiting on the Alex's driver patches?
Can't this be submitted together? And with instructions about how to
test it, which hardware supports it, etc, so that we can try to find
hardware inside our corporate walls and test this as one piece?
I'm almost calling it a day, last thing will be to push what I have in
my perf/core branch, in a few moments.
- Arnaldo
next prev parent reply other threads:[~2015-03-12 20:57 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-07 21:06 [PATCH V5 00/25] perf tools: Introduce an abstraction for Instruction Tracing Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 01/25] perf header: Add Instruction Tracing feature Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 02/25] perf evlist: Add initial support for mmapping an Instruction Trace buffer Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 03/25] perf tools: Add user events for Instruction Tracing Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 04/25] perf tools: Add support for Instruction Trace recording Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 05/25] perf record: Add basic Instruction Tracing support Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 06/25] perf record: Extend -m option for Instruction Tracing mmap pages Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 07/25] perf tools: Add a user event for Instruction Tracing errors Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 08/25] perf session: Add hooks to allow transparent decoding of Instruction Tracing data Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 09/25] perf session: Add Instruction Tracing options Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 10/25] perf itrace: Add helpers for Instruction Tracing errors Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 11/25] perf itrace: Add helpers for queuing Instruction Tracing data Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 12/25] perf itrace: Add a heap for sorting Instruction Tracing queues Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 13/25] perf itrace: Add processing for Instruction Tracing events Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 14/25] perf itrace: Add a hashtable for caching decoded instructions Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 15/25] perf tools: Add member to struct dso for an instruction cache Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 16/25] perf script: Add Instruction Tracing support Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 17/25] perf script: Always allow fields 'addr' and 'cpu' for itrace Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 18/25] perf report: Add Instruction Tracing support Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 19/25] perf inject: Re-pipe Instruction Tracing events Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 20/25] perf inject: Add Instruction Tracing support Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 21/25] perf tools: Add Instruction Tracing index Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 22/25] perf tools: Hit all build ids when Instruction Tracing Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 23/25] perf tools: Add build option NO_ITRACE to exclude " Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 24/25] perf itrace: Add option to synthesize events for transactions Adrian Hunter
2015-03-07 21:06 ` [PATCH V5 25/25] perf script: Add field option 'flags' to print sample flags Adrian Hunter
2015-03-11 15:55 ` [PATCH V5 00/25] perf tools: Introduce an abstraction for Instruction Tracing Adrian Hunter
2015-03-11 19:33 ` Arnaldo Carvalho de Melo
2015-03-12 20:51 ` Adrian Hunter
2015-03-12 20:57 ` Arnaldo Carvalho de Melo [this message]
2015-03-13 11:40 ` Adrian Hunter
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=20150312205725.GJ3550@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=andi.kleen@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.