From: Stephane Eranian <eranian@google.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Andi Kleen <andi@firstfloor.org>, "mingo@elte.hu" <mingo@elte.hu>,
LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Arnaldo Carvalho de Melo <acme@infradead.org>
Subject: Re: Basic perf PMU support for Haswell v6
Date: Tue, 12 Mar 2013 15:13:01 +0100 [thread overview]
Message-ID: <CABPqkBTPv81Lrj6cEUvGA9aMDvPWiC6RZpxxx_TSzGnzDE+9sw@mail.gmail.com> (raw)
In-Reply-To: <20130312135803.GA21741@gmail.com>
On Tue, Mar 12, 2013 at 2:58 PM, Ingo Molnar <mingo@kernel.org> wrote:
>
> * Stephane Eranian <eranian@google.com> wrote:
>
>> Hi,
>>
>> I am not seeing those patches in tip.git tree as of today.
>> What is still wrong with those patches? I think they
>> are good for providing the basic enablement for HSW.
>
> There were still problems with them so they didn't make it
> into v3.9 - now that the development window is open I'll check
> the latest iteration (v9), in a couple of days.
>
Ok, then. We need to move forward with HSW now.
Thanks.
prev parent reply other threads:[~2013-03-12 14:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 22:04 Basic perf PMU support for Haswell v6 Andi Kleen
2013-02-12 22:04 ` [PATCH 1/5] perf, x86: Add Haswell PEBS record support v3 Andi Kleen
2013-02-12 22:04 ` [PATCH 2/5] perf, x86: Basic Haswell PMU support v4 Andi Kleen
2013-02-13 8:16 ` Ingo Molnar
2013-02-12 22:04 ` [PATCH 3/5] perf, x86: Basic Haswell PEBS " Andi Kleen
2013-02-12 22:04 ` [PATCH 4/5] perf, x86: Support full width counting v3 Andi Kleen
2013-02-12 22:04 ` [PATCH 5/5] perf, x86: Move NMI clearing to end of PMI handler after the counter registers are reset Andi Kleen
2013-03-12 13:02 ` Basic perf PMU support for Haswell v6 Stephane Eranian
2013-03-12 13:58 ` Ingo Molnar
2013-03-12 14:13 ` Stephane Eranian [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=CABPqkBTPv81Lrj6cEUvGA9aMDvPWiC6RZpxxx_TSzGnzDE+9sw@mail.gmail.com \
--to=eranian@google.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@infradead.org \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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;
as well as URLs for NNTP newsgroup(s).