From: Peter Zijlstra <peterz@infradead.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: "Yan, Zheng" <zheng.z.yan@intel.com>,
linux-kernel@vger.kernel.org, eranian@google.com
Subject: Re: [RFC PATCH 0/7] perf, x86: Reduce lbr_sel_map size
Date: Fri, 4 Oct 2013 16:42:14 +0200 [thread overview]
Message-ID: <20131004144214.GL3081@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20131004133548.GF6882@two.firstfloor.org>
On Fri, Oct 04, 2013 at 03:35:48PM +0200, Andi Kleen wrote:
> > From what I can tell this is the exact same drivel I rejected earlier.
>
> So what do you want changed?
Maybe go read what I wrote last time? AFAICT there's nothing different
and the changelogs for sure don't say anything useful.
prev parent reply other threads:[~2013-10-04 14:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-26 8:28 [RFC PATCH 0/7] perf, x86: Reduce lbr_sel_map size Yan, Zheng
2013-09-26 8:28 ` [RFC PATCH 1/7] " Yan, Zheng
2013-09-26 8:28 ` [RFC PATCH 2/7] perf, x86: Basic Haswell LBR call stack support Yan, Zheng
2013-09-26 8:28 ` [RFC PATCH 3/7] perf, core: replace flush_branch_stack with ctxsw callback Yan, Zheng
2013-09-26 8:28 ` [RFC PATCH 4/7] perf, x86: Save/resotre LBR stack during context switch Yan, Zheng
2013-09-26 8:28 ` [RFC PATCH 5/7] perf, core: Pass perf_sample_data to perf_callchain() Yan, Zheng
2013-09-26 8:28 ` [RFC PATCH 6/7] perf, x86: Use LBR call stack to get user callchain Yan, Zheng
2013-09-26 8:28 ` [RFC PATCH 7/7] perf, x86: Discard zero length call entries in LBR call stack Yan, Zheng
2013-10-04 10:55 ` [RFC PATCH 0/7] perf, x86: Reduce lbr_sel_map size Peter Zijlstra
2013-10-04 13:35 ` Andi Kleen
2013-10-04 14:42 ` Peter Zijlstra [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=20131004144214.GL3081@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=andi@firstfloor.org \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zheng.z.yan@intel.com \
/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