From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, kan.liang@linux.intel.com
Subject: Re: [PATCH v6 0/7] perf, intel: Add support for PEBS output to Intel PT
Date: Tue, 6 Aug 2019 11:43:15 -0300 [thread overview]
Message-ID: <20190806144315.GA2460@redhat.com> (raw)
In-Reply-To: <20190806143032.GU2332@hirez.programming.kicks-ass.net>
Em Tue, Aug 06, 2019 at 04:30:32PM +0200, Peter Zijlstra escreveu:
> On Tue, Aug 06, 2019 at 11:45:59AM +0300, Alexander Shishkin wrote:
>
> > Seventh attempt at the PEBS-via-PT feature. The previous ones were [1], [2],
> > [3], [4], [5], [6]. This one finalizes the 'aux_output' naming in the code.
>
> > Alexander Shishkin (2):
> > perf: Allow normal events to output AUX data
> > perf/x86/intel: Support PEBS output to PT
>
> Thanks Alexander!, I've picked up the above two patches.
>
> > Adrian Hunter (5):
> > perf tools: Add aux_output attribute flag
> > perf tools: Add itrace option 'o' to synthesize aux-output events
> > perf intel-pt: Process options for PEBS event synthesis
> > perf tools: Add aux-output config term
> > perf intel-pt: Add brief documentation for PEBS via Intel PT
>
> Arnaldo, can you either ack (in which case I'll pick them up) or
> otherwise take care of these?
Lemme pick those, so that it goes thru the container build tests, etc.
- Arnaldo
prev parent reply other threads:[~2019-08-06 14:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 8:45 [PATCH v6 0/7] perf, intel: Add support for PEBS output to Intel PT Alexander Shishkin
2019-08-06 8:46 ` [PATCH v6 1/7] perf: Allow normal events to output AUX data Alexander Shishkin
2019-08-28 13:30 ` [tip: perf/core] " tip-bot2 for Alexander Shishkin
2019-08-06 8:46 ` [PATCH v6 2/7] perf/x86/intel: Support PEBS output to PT Alexander Shishkin
2019-08-28 13:30 ` [tip: perf/core] " tip-bot2 for Alexander Shishkin
2019-08-06 8:46 ` [PATCH v6 3/7] perf tools: Add aux_output attribute flag Alexander Shishkin
2019-08-15 9:30 ` [tip:perf/core] " tip-bot for Adrian Hunter
2019-08-06 8:46 ` [PATCH v6 4/7] perf tools: Add itrace option 'o' to synthesize aux-output events Alexander Shishkin
2019-08-15 9:30 ` [tip:perf/core] " tip-bot for Adrian Hunter
2019-08-06 8:46 ` [PATCH v6 5/7] perf intel-pt: Process options for PEBS event synthesis Alexander Shishkin
2019-08-15 9:31 ` [tip:perf/core] " tip-bot for Adrian Hunter
2019-08-06 8:46 ` [PATCH v6 6/7] perf tools: Add aux-output config term Alexander Shishkin
2019-08-15 9:32 ` [tip:perf/core] " tip-bot for Adrian Hunter
2019-08-06 8:46 ` [PATCH v6 7/7] perf intel-pt: Add brief documentation for PEBS via Intel PT Alexander Shishkin
2019-08-13 13:51 ` Arnaldo Carvalho de Melo
2019-08-13 14:05 ` Alexander Shishkin
2019-08-13 14:14 ` Arnaldo Carvalho de Melo
2019-08-13 16:21 ` Alexander Shishkin
2019-08-15 9:33 ` [tip:perf/core] " tip-bot for Adrian Hunter
2019-08-06 14:30 ` [PATCH v6 0/7] perf, intel: Add support for PEBS output to " Peter Zijlstra
2019-08-06 14:43 ` Arnaldo Carvalho de Melo [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=20190806144315.GA2460@redhat.com \
--to=acme@redhat.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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).