From: Andi Kleen <ak@linux.intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Kan Liang <kan.liang@intel.com>,
mingo@kernel.org, acme@infradead.org, eranian@google.com,
andi@firstfloor.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] perf, pebs: Add PEBS v3 record decoding
Date: Tue, 12 May 2015 11:08:37 -0700 [thread overview]
Message-ID: <20150512180837.GD13605@tassilo.jf.intel.com> (raw)
In-Reply-To: <20150512132557.GQ21418@twins.programming.kicks-ass.net>
On Tue, May 12, 2015 at 03:25:57PM +0200, Peter Zijlstra wrote:
>
>
> So seeing how I have both this series and Andi's SKL patches, I did the
> below on top of them both.
>
> Could someone try that?
I did a quick test and didn't see any problems.
Tested-by: Andi Kleen <ak@linux.intel.com>
-Andi
next prev parent reply other threads:[~2015-05-12 18:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-10 19:13 [PATCH V9 0/8] large PEBS interrupt threshold Kan Liang
2015-05-10 19:13 ` [PATCH V9 1/8] perf, x86: use the PEBS auto reload mechanism when possible Kan Liang
2015-05-10 19:13 ` [PATCH V9 2/8] perf, x86: introduce setup_pebs_sample_data() Kan Liang
2015-05-10 19:13 ` [PATCH V9 3/8] perf, x86: handle multiple records in PEBS buffer Kan Liang
2015-05-12 13:25 ` [RFC][PATCH] perf, pebs: Add PEBS v3 record decoding Peter Zijlstra
2015-05-12 18:08 ` Andi Kleen [this message]
2015-05-13 1:31 ` Liang, Kan
2015-05-10 19:13 ` [PATCH V9 4/8] perf, x86: large PEBS interrupt threshold Kan Liang
2015-05-10 19:13 ` [PATCH V9 5/8] perf, x86: drain PEBS buffer during context switch Kan Liang
2015-05-10 19:13 ` [PATCH V9 6/8] perf, x86: enlarge PEBS buffer Kan Liang
2015-05-10 19:13 ` [PATCH V9 7/8] perf, x86: introduce PERF_RECORD_LOST_SAMPLES Kan Liang
2015-05-11 19:06 ` Arnaldo Carvalho de Melo
2015-06-07 17:50 ` [tip:perf/core] perf/x86/intel: Introduce PERF_RECORD_LOST_SAMPLES tip-bot for Kan Liang
2015-05-10 19:13 ` [PATCH V9 8/8] perf tools: handle PERF_RECORD_LOST_SAMPLES Kan Liang
2015-05-11 19:22 ` Arnaldo Carvalho de Melo
2015-05-11 20:40 ` Liang, Kan
2015-05-11 21:27 ` Arnaldo Carvalho de Melo
2015-05-12 12:43 ` Peter Zijlstra
2015-05-12 13:04 ` Arnaldo Carvalho de Melo
2015-06-07 17:51 ` [tip:perf/core] " tip-bot for Kan Liang
2015-05-11 16:06 ` [PATCH V9 0/8] large PEBS interrupt threshold Peter Zijlstra
2015-05-11 16:08 ` Liang, Kan
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=20150512180837.GD13605@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=acme@infradead.org \
--cc=andi@firstfloor.org \
--cc=eranian@google.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.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.