From: Sukadev Bhattiprolu <sukadev@linux•vnet.ibm.com>
To: Michael Ellerman <michael@ellerman•id.au>
Cc: Andi Kleen <ak@linux•intel.com>,
Peter Zijlstra <a.p.zijlstra@chello•nl>,
robert.richter@amd•com, Anton Blanchard <anton@au1•ibm.com>,
linux-kernel@vger•kernel.org,
Stephane Eranian <eranian@google•com>,
linuxppc-dev@ozlabs•org, Ingo Molnar <mingo@redhat•com>,
Paul Mackerras <paulus@samba•org>,
Arnaldo Carvalho de Melo <acme@ghostprotocols•net>,
Jiri Olsa <jolsa@redhat•com>
Subject: Re: [PATCH 5/6][v4]: perf: Create a sysfs entry for Power event format
Date: Tue, 26 Feb 2013 12:03:43 -0800 [thread overview]
Message-ID: <20130226200343.GA21543@us.ibm.com> (raw)
In-Reply-To: <20130226052646.GB21553@concordia>
Michael Ellerman [michael@ellerman•id.au] wrote:
| On Tue, Jan 22, 2013 at 10:26:13PM -0800, Sukadev Bhattiprolu wrote:
| >
| > [PATCH 5/6][v4]: perf: Create a sysfs entry for Power event format
| >
| > Create a sysfs entry, '/sys/bus/event_source/devices/cpu/format/event'
| > which describes the format of a POWER cpu.
|
| Did this patch go upstream? I don't see it.
Hmm, patches 1..4,6 are in linux-tip and Arnaldo's trees but patch 5 is
in neither.
|
| If not, please don't merge it.
|
| > The format of the event is the same for all POWER cpus at least in
| > (Power6, Power7), so bulk of this change is common in the code common
| > to POWER cpus.
|
| No. The event format is different on most POWER cpus, in particular it
| is different on Power6 and Power7, and will be different again on
| Power8.
Sigh. The port of this patchset to Power6 has not started yet.
But this patchset does work on Power7 correct ?
If so, and we figure out what happened to patch 5, can we add a patch to
to move the format code to power7-pmu.c ?
Sukadev
next prev parent reply other threads:[~2013-02-26 20:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 6:22 [PATCH 0/6][v4]: perf: Make POWER7 events available in sysfs Sukadev Bhattiprolu
2013-01-23 6:23 ` [PATCH 1/6][v4]: perf/Power7: Use macros to identify perf events Sukadev Bhattiprolu
2013-01-23 6:24 ` [PATCH 2/6][v4]: perf: Make EVENT_ATTR global Sukadev Bhattiprolu
2013-01-23 6:24 ` [PATCH 3/6][v4]: perf/POWER7: Make generic event translations available in sysfs Sukadev Bhattiprolu
2013-01-23 6:25 ` [PATCH 4/6][v4]: perf/POWER7: Make some POWER7 events " Sukadev Bhattiprolu
2013-01-23 6:26 ` [PATCH 5/6][v4]: perf: Create a sysfs entry for Power event format Sukadev Bhattiprolu
2013-02-26 5:26 ` Michael Ellerman
2013-02-26 20:03 ` Sukadev Bhattiprolu [this message]
2013-02-27 1:17 ` Michael Ellerman
2013-03-06 5:48 ` Sukadev Bhattiprolu
2013-03-12 9:27 ` Paul Mackerras
2013-03-13 0:15 ` Michael Ellerman
2013-02-27 1:27 ` Michael Ellerman
2013-01-23 6:26 ` [PATCH 6/6][v4]: perf: Document the ABI of perf sysfs entries Sukadev Bhattiprolu
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=20130226200343.GA21543@us.ibm.com \
--to=sukadev@linux$(echo .)vnet.ibm.com \
--cc=a.p.zijlstra@chello$(echo .)nl \
--cc=acme@ghostprotocols$(echo .)net \
--cc=ak@linux$(echo .)intel.com \
--cc=anton@au1$(echo .)ibm.com \
--cc=eranian@google$(echo .)com \
--cc=jolsa@redhat$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=michael@ellerman$(echo .)id.au \
--cc=mingo@redhat$(echo .)com \
--cc=paulus@samba$(echo .)org \
--cc=robert.richter@amd$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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