linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Runzhen Wang <runzhen@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Cc: acme@redhat.com, xiaoguangrong@linux.vnet.ibm.com,
	paulus@samba.org, Runzhen Wang <runzhen@linux.vnet.ibm.com>,
	sukadev@linux.vnet.ibm.com
Subject: [PATCH v2 0/2] perf tools: Power7 events name available for perf
Date: Tue, 25 Jun 2013 22:35:31 +0800	[thread overview]
Message-ID: <1372170933-4538-1-git-send-email-runzhen@linux.vnet.ibm.com> (raw)

Thank for Sukadev Bhattip and Xiao Guangrong's help.
Thank for Michael Ellerman's review. 

There is the Change Log for v2:

1. As Michael Ellerman suggested, I added runtime overhead information 
   in the 0002 patch's description.

2. Put the events name in a new head file which is named "power7-events-list.h",
   and use several macros, such as, 
 
   #define EVENT(_name, _code)     POWER_EVENT_ATTR(_name, _code)
   #include "power7-events-list.h"
   #undef EVENT
  
   to generate different outputs.
 
Thanks
Runzhen Wang

Runzhen Wang (2):
  perf tools: fix a typo of a Power7 event name
  perf tools: Make Power7 events available for perf

 .../testing/sysfs-bus-event_source-devices-events  |    2 +-
 arch/powerpc/include/asm/perf_event_server.h       |    4 +-
 arch/powerpc/perf/power7-events-list.h             |  548 ++++++++++++++++++++
 arch/powerpc/perf/power7-pmu.c                     |  150 ++----
 4 files changed, 584 insertions(+), 120 deletions(-)
 create mode 100644 arch/powerpc/perf/power7-events-list.h

-- 
1.7.9.5

             reply	other threads:[~2013-06-25 14:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-25 14:35 Runzhen Wang [this message]
2013-06-25 14:35 ` [PATCH v3 1/2] perf tools: fix a typo of a Power7 event name Runzhen Wang
2013-06-27 14:26   ` Michael Ellerman
2013-06-25 14:35 ` [PATCH v2 2/2] perf tools: Make Power7 events available for perf Runzhen Wang
2013-06-25 16:46   ` Vince Weaver
2013-07-04 12:52     ` Michael Ellerman
2013-07-04 12:57       ` Peter Zijlstra
2013-07-05 10:23         ` Ingo Molnar
2013-07-09  1:29         ` Michael Ellerman
2013-07-09  2:24           ` Vince Weaver
2013-07-09  3:34             ` Michael Ellerman
2013-07-09 15:20               ` Vince Weaver
2013-07-10  2:37                 ` Michael Ellerman
2013-07-09  8:14             ` Peter Zijlstra
2013-07-09 15:05               ` Vince Weaver
2013-07-11 10:58                 ` Will Deacon
2013-07-11 17:53                   ` Vince Weaver
2013-07-10  3:09               ` Michael Ellerman
2013-07-10  8:34                 ` Ingo Molnar
2013-07-11  4:42                   ` Vince Weaver
2013-07-11  6:58                     ` Michael Ellerman
2013-06-27 14:23   ` Michael Ellerman

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=1372170933-4538-1-git-send-email-runzhen@linux.vnet.ibm.com \
    --to=runzhen@linux.vnet.ibm.com \
    --cc=acme@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=paulus@samba.org \
    --cc=sukadev@linux.vnet.ibm.com \
    --cc=xiaoguangrong@linux.vnet.ibm.com \
    /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).