From: Peter Zijlstra <peterz@infradead.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: acma@infradead.org, mingo@kernel.org,
linux-kernel@vger.kernel.org, jolsa@redhat.com
Subject: Re: perf, x86: Add last TSX PMU code for Haswell v3
Date: Tue, 1 Oct 2013 10:04:12 +0200 [thread overview]
Message-ID: <20131001080412.GK3081@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20131001073124.GF6931@two.firstfloor.org>
On Tue, Oct 01, 2013 at 09:31:24AM +0200, Andi Kleen wrote:
> Sorry I missed that. No change other than acks/rebase,
> so the previous version should be fine. Thanks.
Yeah, I didn't mail out and it hasn't landed it -tip yet. So you
couldn't have known.
> Outstanding TSX patches i have now (unless someone merged them):
>
> perf stat -T
>
> https://lkml.org/lkml/2013/8/21/667
>
> Was acked by Arnaldo
>
> 64bit comparison fix without that the abort code reporting with
> the abort code in the high 32bit doesn't work.
>
> https://lkml.org/lkml/2013/9/27/569
>
> Acked by Namyoung.
Both are tools patches; I'll see if I can get acme to pick them up; if
not I'll pick them up.
prev parent reply other threads:[~2013-10-01 8:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-30 21:58 Andi Kleen
2013-09-30 21:58 ` [PATCH 1/6] perf, core: Add generic transaction flags v5 Andi Kleen
2013-09-30 21:58 ` [PATCH 2/6] perf, x86: Add Haswell specific transaction flag reporting v5 Andi Kleen
2013-09-30 21:59 ` [PATCH 3/6] perf, tools: Support sorting by in_tx, abort branch flags v3 Andi Kleen
2013-09-30 21:59 ` [PATCH 4/6] perf, tools: Add abort_tx,no_tx,in_tx branch filter options to perf record -j v3 Andi Kleen
2013-09-30 21:59 ` [PATCH 5/6] perf, tools: Add support for record transaction flags v5 Andi Kleen
2013-09-30 21:59 ` [PATCH 6/6] perf, x86: Suppress duplicated abort LBR records v2 Andi Kleen
2013-10-01 7:22 ` perf, x86: Add last TSX PMU code for Haswell v3 Peter Zijlstra
2013-10-01 7:31 ` Andi Kleen
2013-10-01 8:04 ` 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=20131001080412.GK3081@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acma@infradead.org \
--cc=andi@firstfloor.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.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
Powered by JetHome