From: Jan Ceuleers <jan.ceuleers@computer.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: acme@redhat.com, jolsa@redhat.com, eranian@google.com,
a.p.zijlstra@chello.nl, linux-kernel@vger.kernel.org
Subject: Re: Tie lose "perf, tools" ends in Haswell PMU patchkit
Date: Sat, 06 Oct 2012 16:57:20 +0200 [thread overview]
Message-ID: <507046D0.8090408@computer.org> (raw)
In-Reply-To: <1349299363-30714-1-git-send-email-andi@firstfloor.org>
On 10/03/2012 11:22 PM, Andi Kleen wrote:
> This fixes some left over issues in my Haswell PMU patchkit yesterday:
> Ideally applied on top, although there should be no direct dependencies.
>
> - Now the kernel supplied sysfs aliases can be directly used for cpu.
> This means I can use "tx-aborts" instead of "cpu/tx-aborts/
> - List the kernel events
> - Support using the same names as generic events for kernel events.
> This allows to use cpu/instructions,intx=1/ which was not possible
> before because instructions clashed with the generic name.
I (i.e. me, moi) received only patches 2/3 and 3/3. Is there a patch 1/3?
next prev parent reply other threads:[~2012-10-06 15:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 21:22 Tie lose "perf, tools" ends in Haswell PMU patchkit Andi Kleen
2012-10-03 21:22 ` [PATCH 1/3] perf, tools: Support generic events as pmu event names Andi Kleen
2012-10-03 21:22 ` [PATCH 2/3] perf, tools: Default to cpu// for events Andi Kleen
2012-10-03 21:22 ` [PATCH 3/3] perf, tools: List kernel supplied event aliases in perf list Andi Kleen
2012-10-06 14:57 ` Jan Ceuleers [this message]
2012-10-06 17:34 ` Tie lose "perf, tools" ends in Haswell PMU patchkit Andi Kleen
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=507046D0.8090408@computer.org \
--to=jan.ceuleers@computer.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=andi@firstfloor.org \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.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 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.