From: Peter Zijlstra <peterz@infradead.org>
To: "Liang, Kan" <kan.liang@intel.com>
Cc: Jiri Olsa <jolsa@redhat.com>, "acme@kernel.org" <acme@kernel.org>,
"eranian@google.com" <eranian@google.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"paulus@samba.org" <paulus@samba.org>,
"ak@linux.intel.com" <ak@linux.intel.com>,
"namhyung@kernel.org" <namhyung@kernel.org>
Subject: Re: [PATCH V5 0/3] perf tool: Haswell LBR call stack support (user)
Date: Mon, 5 Jan 2015 14:57:48 +0100 [thread overview]
Message-ID: <20150105135748.GT30905@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <37D7C6CF3E00A74B8858931C1DB2F0770167D124@shsmsx102.ccr.corp.intel.com>
On Thu, Dec 04, 2014 at 02:49:52PM +0000, Liang, Kan wrote:
> > I'll test it once I get hands on Haswel server again, I guess we wait for the
> > kernel change to go in first anyway, right?
> >
>
> I'm not sure, let's ask Peter.
>
> Peter?
Ok so only 3/3 was missing right? I handed the kernel bits to Ingo when
I 'left' with a note that userspace was pending. It seems that is now
resolved.
I stuck 3/3 at the end (it seems to still apply -- yay!) and will send
it together with the kernel bits.
next prev parent reply other threads:[~2015-01-05 13:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 15:06 [PATCH V5 0/3] perf tool: Haswell LBR call stack support (user) kan.liang
2014-12-02 15:06 ` [PATCH V5 1/3] perf tools: enable LBR call stack support kan.liang
2014-12-12 8:17 ` [tip:perf/urgent] perf callchain: Fixup parameter handling error message tip-bot for Kan Liang
2014-12-02 15:06 ` [PATCH V5 2/3] perf tool: Move cpumode resolve code to add_callchain_ip kan.liang
2014-12-12 8:18 ` [tip:perf/urgent] perf callchain: " tip-bot for Kan Liang
2014-12-02 15:06 ` [PATCH V5 3/3] perf tools: Construct LBR call chain kan.liang
2014-12-04 14:23 ` [PATCH V5 0/3] perf tool: Haswell LBR call stack support (user) Jiri Olsa
2014-12-04 14:49 ` Liang, Kan
2014-12-04 15:51 ` Arnaldo Carvalho de Melo
2014-12-04 16:02 ` Jiri Olsa
2014-12-04 16:18 ` Liang, Kan
2014-12-09 12:27 ` Arnaldo Carvalho de Melo
2014-12-09 12:53 ` Jiri Olsa
2014-12-09 13:11 ` Arnaldo Carvalho de Melo
2014-12-09 13:22 ` Jiri Olsa
2014-12-09 13:27 ` Arnaldo Carvalho de Melo
2014-12-09 13:33 ` Jiri Olsa
2015-01-05 13:57 ` Peter Zijlstra [this message]
2015-01-05 15:58 ` Liang, Kan
2014-12-11 22:21 ` Jiri Olsa
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=20150105135748.GT30905@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=paulus@samba.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