public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Jiri Olsa <jolsa@redhat.com>
Cc: acme@redhat.com, mingo@elte.hu, paulus@samba.org,
	cjashfor@linux.vnet.ibm.com, fweisbec@gmail.com,
	eranian@google.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/6] perf, x86: Making hardware events tranlations sysfs available
Date: Thu, 14 Jun 2012 23:09:52 +0200	[thread overview]
Message-ID: <1339708192.2559.40.camel@twins> (raw)
In-Reply-To: <1339706321-8802-2-git-send-email-jolsa@redhat.com>

On Thu, 2012-06-14 at 22:38 +0200, Jiri Olsa wrote:
> Making hardware events tranlations available throught the sysfs.
> Adding 'events' group attribute under the sysfs x86 PMU record
> with attribute/file for each hardware event:
> 
>   # ls  /sys/devices/cpu/events/
>   branch_instructions
>   branch_misses
>   bus_cycles
>   cache_misses
>   cache_references
>   cycles
>   instructions
>   ref_cycles
>   stalled_cycles_backend
>   stalled_cycles_frontend
> 
> The file - ID mappings is:
> 
>   file                      hw id
>   ----------------------------------------------------------------
>   cycles                    PERF_COUNT_HW_CPU_CYCLES
>   instructions              PERF_COUNT_HW_INSTRUCTIONS
>   cache_references          PERF_COUNT_HW_CACHE_REFERENCES
>   cache_misses              PERF_COUNT_HW_CACHE_MISSES
>   branch_instructions       PERF_COUNT_HW_BRANCH_INSTRUCTIONS
>   branch_misses             PERF_COUNT_HW_BRANCH_MISSES
>   bus_cycles                PERF_COUNT_HW_BUS_CYCLES
>   stalled_cycles_frontend   PERF_COUNT_HW_STALLED_CYCLES_FRONTEND
>   stalled_cycles_backend    PERF_COUNT_HW_STALLED_CYCLES_BACKEND
>   ref_cycles                PERF_COUNT_HW_REF_CPU_CYCLES
> 
> Each attribute/file contains HW ID event translation for the currently
> running CPU model
> 
>   # cat /sys/devices/cpu/events/instructions
>   0xc0

Why not have it consistent with the stuff done for uncore where events
read: 'event=0xc0', ie the regular field=value stuff.



  reply	other threads:[~2012-06-14 21:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-14 20:38 [RFC 0/6] perf, tool: Allow to use hw events in PMU syntax Jiri Olsa
2012-06-14 20:38 ` [PATCH 1/6] perf, x86: Making hardware events tranlations sysfs available Jiri Olsa
2012-06-14 21:09   ` Peter Zijlstra [this message]
2012-06-14 21:36     ` Stephane Eranian
2012-06-15  7:29       ` Jiri Olsa
2012-06-15  7:32         ` Stephane Eranian
2012-06-15  7:43           ` Jiri Olsa
2012-06-15  7:46             ` Stephane Eranian
2012-06-15  9:26               ` Peter Zijlstra
2012-06-14 20:38 ` [PATCH 2/6] perf tools: Fix generation of pmu list Jiri Olsa
2012-07-06 10:58   ` [tip:perf/core] " tip-bot for Robert Richter
2012-06-14 20:38 ` [PATCH 3/6] perf, tool: Properly free format data Jiri Olsa
2012-06-14 20:38 ` [PATCH 4/6] perf, tool: Add events support for pmu Jiri Olsa
2012-06-29 16:36   ` Arnaldo Carvalho de Melo
2012-06-29 16:43     ` Jiri Olsa
2012-06-14 20:38 ` [PATCH 5/6] perf, tool: event parsing - split PE_VALUE_SYM to SW and HW tokens Jiri Olsa
2012-06-14 20:38 ` [PATCH 6/6] perf, tool: Support translate terms for hw events Jiri Olsa

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=1339708192.2559.40.camel@twins \
    --to=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=cjashfor@linux.vnet.ibm.com \
    --cc=eranian@google.com \
    --cc=fweisbec@gmail.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox