linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anshuman Khandual <khandual@linux.vnet.ibm.com>
To: "Yan, Zheng" <zheng.z.yan@intel.com>
Cc: a.p.zijlstra@chello.nl, mingo@elte.hu, andi@firstfloor.org,
	eranian@google.com, jolsa@redhat.com, ming.m.lin@intel.com,
	gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V4 0/10] perf: Intel uncore pmu counting support
Date: Mon, 04 Jun 2012 15:05:57 +0530	[thread overview]
Message-ID: <4FCC817D.5060206@linux.vnet.ibm.com> (raw)
In-Reply-To: <1337144403-30841-1-git-send-email-zheng.z.yan@intel.com>

aOn Wednesday 16 May 2012 10:29 AM, Yan, Zheng wrote:

> Hi, all
> 
> Here is the V4 patches to add uncore counting support for Nehalem,
> Sandy Bridge and Sandy Bridge-EP, applied on top of current tip.
> The code is based on Lin Ming's old patches.
> 
> For Nehalem and Sandy Bridge-EP, A few general events are exported
> under sysfs directory:
>   /sys/bus/event_source/devices/${uncore_dev}/events/
> 
> Each file in the events directory defines an event. The content is
> a string such as:
>   config=1,config1=2
> 
> You can use 'perf stat' to access to the uncore pmu. For example:
>   perf stat -a -C 0 -e 'Uncore_iMC_0/CAS_COUNT_RD/' sleep 1

Hello Yan, 

When I boot my Sandy bridge laptop with the patchset applied, I can see the following
directories in my sysfs interface here at /sys/bus/event_source/devices

-------------------------------------------------------
breakpoint  software    Uncore_C-Box_0  Uncore_C-Box_2
cpu         tracepoint  Uncore_C-Box_1  Uncore_C-Box_3
-------------------------------------------------------

So looks like I have 4 C-Box kind of uncore PMUs present on my system. But it does not
have "events" directory which is suppose to hold the events related to C-box pmu. This
is in line with you what you have mentioned above, generic events are only exported for
Nehalem and Sandy Bridge-EP type processors. I guess there are number of RAW events
associated with C-box type PMU. I am not able to figure out how to use those RAW events
directly in "perf stat". Could you please guide me how to use them in a sandy bridge setup
as I have explained above. Thank you.

Regards,
Anshuman Khandual


      parent reply	other threads:[~2012-06-04  9:36 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-16  4:59 [PATCH V4 0/10] perf: Intel uncore pmu counting support Yan, Zheng
2012-05-16  4:59 ` [PATCH 01/10] perf: Export perf_assign_events Yan, Zheng
2012-05-16  4:59 ` [PATCH 02/10] perf: Avoid race between cpu hotplug and installing event Yan, Zheng
2012-05-16  4:59 ` [PATCH 03/10] perf: Allow pmu to choose cpu on which to install event Yan, Zheng
2012-05-16  4:59 ` [PATCH 04/10] perf: Introduce perf_pmu_migrate_context Yan, Zheng
2012-05-16  4:59 ` [PATCH 05/10] perf: Generic intel uncore support Yan, Zheng
2012-05-16  4:59 ` [PATCH 06/10] perf: Add Nehalem and Sandy Bridge " Yan, Zheng
2012-05-16  5:00 ` [PATCH 07/10] perf: Generic pci uncore device support Yan, Zheng
2012-05-16  5:00 ` [PATCH 08/10] perf: Add Sandy Bridge-EP uncore support Yan, Zheng
2012-05-16  5:00 ` [PATCH 09/10] perf tool: Make the event parser reentrantable Yan, Zheng
2012-05-16  5:00 ` [PATCH 10/10] perf tool: Add pmu event alias support Yan, Zheng
2012-05-21  7:36 ` [RFC 0/5] perf, tool: uncore related changes Jiri Olsa
2012-05-21  7:36   ` [PATCH 1/5] perf, tool: Use data struct for arg passing in event parse function Jiri Olsa
2012-05-21  7:36   ` [PATCH 2/5] perf, tool: Make the event parser reentrantable Jiri Olsa
2012-05-21  7:36   ` [PATCH 3/5] perf, tool: Add support to reuse event grammar to parse out terms Jiri Olsa
2012-05-21  7:36   ` [PATCH 4/5] perf, tool: Add pmu event alias support Jiri Olsa
2012-05-21  7:36   ` [PATCH 5/5] perf, tool: Add automated test for pure terms parsing Jiri Olsa
2012-05-21  8:22   ` [RFC 0/5] perf, tool: uncore related changes Jiri Olsa
2012-05-23 14:53   ` Stephane Eranian
2012-05-23 15:16     ` Jiri Olsa
2012-05-23 15:21       ` Stephane Eranian
2012-05-23 15:28         ` Jiri Olsa
2012-06-04  9:35 ` Anshuman Khandual [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=4FCC817D.5060206@linux.vnet.ibm.com \
    --to=khandual@linux.vnet.ibm.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=andi@firstfloor.org \
    --cc=eranian@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.m.lin@intel.com \
    --cc=mingo@elte.hu \
    --cc=zheng.z.yan@intel.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).