All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yan, Zheng" <zheng.z.yan@intel.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Ingo Molnar <mingo@kernel.org>,
	mingo@elte.hu, andi@firstfloor.org, eranian@google.com,
	linux-kernel@vger.kernel.org, ming.m.lin@intel.com,
	Jiri Olsa <jolsa@redhat.com>,
	Arnaldo Carvalho de Melo <acme@infradead.org>
Subject: Re: [RFC PATCH 0/5] perf: Intel uncore pmu counting support
Date: Wed, 28 Mar 2012 17:02:49 +0800	[thread overview]
Message-ID: <4F72D3B9.1070101@intel.com> (raw)
In-Reply-To: <1332924580.2528.18.camel@twins>

On 03/28/2012 04:49 PM, Peter Zijlstra wrote:
> On Wed, 2012-03-28 at 08:49 +0200, Ingo Molnar wrote:
>> * Yan, Zheng <zheng.z.yan@intel.com> wrote:
>>
>>> Hi, all
>>>
>>> Here is the RFC 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.
>>>
>>> You can use 'perf stat' to access to the uncore pmu. For example:
>>> perf stat -a -C 0 -e 'uncore_nhm/config=0xffff/' sleep 1
>>
>> My main complaint is that that's not user friendly *AT ALL*.
>>
>> You need to make this useful to mere mortals: go through the 
>> SDM, categorize interesting looking events, look at how it can 
>> be expressed via tooling, add a generic event where appropriate, 
>> provide examples, actually *USE* it to improve the kernel or an 
>> app and see the workflow as it happens and improve the tooling, 
>> etc.
> 
> Easiest way out here is add a /sys/bus/event_source/devices/*/events/
> directory which contains files who's name we can use as events and who's
> contents are of the form we would use given the format/ stuff.
> 
> Example, suppose a westmere,
> 
> $ cat /sys/bus/event_source/devices/cpu/events/frontend_stalled_cycles
> event=0x0e,umask=0x01,inv,cmask=1
> 
> I'll review the uncore patches later this week, but I suspect the whole
> cpu->node mapping stuff is still not done properly.
> 
> Also, quick question, did Intel fix the SNB uncore PMI?
No. furthermore there is completely no uncore PMI in Sandy Bridge-EP

Thanks.

  reply	other threads:[~2012-03-28  9:03 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-28  6:43 [RFC PATCH 0/5] perf: Intel uncore pmu counting support Yan, Zheng
2012-03-28  6:43 ` [PATCH 1/5] perf: Export perf_assign_events Yan, Zheng
2012-03-28  6:43 ` [PATCH 2/5] perf: generic intel uncore support Yan, Zheng
2012-03-28  9:24   ` Andi Kleen
2012-03-28  9:38     ` Peter Zijlstra
2012-03-28 11:24     ` Yan, Zheng
2012-03-31  3:18   ` Peter Zijlstra
2012-04-01  3:11     ` Yan, Zheng
2012-04-02 22:10       ` Peter Zijlstra
2012-04-02 22:11       ` Peter Zijlstra
2012-04-03  8:28         ` Yan, Zheng
2012-04-03 14:29           ` Peter Zijlstra
2012-04-04  1:47             ` Yan, Zheng
2012-04-10  0:48             ` Yan, Zheng
2012-04-16 12:11               ` Peter Zijlstra
2012-04-02 22:16       ` Peter Zijlstra
2012-04-02 22:24       ` Peter Zijlstra
2012-04-16 12:07       ` Peter Zijlstra
2012-04-17  6:56         ` Yan, Zheng
2012-03-28  6:43 ` [PATCH 3/5] perf: Add Nehalem and Sandy Bridge " Yan, Zheng
2012-03-28  6:43 ` [PATCH 4/5] perf: Generic pci uncore device support Yan, Zheng
2012-03-28  6:43 ` [PATCH 5/5] perf: Add Sandy Bridge-EP uncore support Yan, Zheng
2012-03-28  6:49 ` [RFC PATCH 0/5] perf: Intel uncore pmu counting support Ingo Molnar
2012-03-28  8:49   ` Peter Zijlstra
2012-03-28  9:02     ` Yan, Zheng [this message]
2012-03-28  8:57   ` Andi Kleen
2012-03-28  9:30     ` Ingo Molnar
2012-03-28 10:58     ` Peter Zijlstra

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=4F72D3B9.1070101@intel.com \
    --to=zheng.z.yan@intel.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@infradead.org \
    --cc=andi@firstfloor.org \
    --cc=eranian@google.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.m.lin@intel.com \
    --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 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.