public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: peterz@infradead.org (Peter Zijlstra)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH/RFC v1 0/2] Human readable performance event description in sysfs
Date: Wed, 20 Jan 2010 14:39:39 +0100	[thread overview]
Message-ID: <1263994779.4283.1057.camel@laptop> (raw)
In-Reply-To: <20100120133145.GE4089@wear.picochip.com>

On Wed, 2010-01-20 at 13:31 +0000, Jamie Iles wrote:
> Personally I think this is a good idea. At the moment 'perf list' gives lots
> of events that the system isn't capable of counting. Admittedly it's fairly
> easy to see if they are supported but it would be nice if the list reflected
> the countable events. perf already does this for the tracing events so it
> would be nice if it did the same for the hardware events. I guess the same
> hierarchy would be nice too. 

This seems to be missing the patch that extends perf list to report the
support and counting status for the events on the current machine :-)

Furthermore, /proc/cpuinfo should be enough information to come up with
an arch specific set of events to be translated into raw.

  reply	other threads:[~2010-01-20 13:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-20  9:11 [PATCH/RFC v1 0/2] Human readable performance event description in sysfs Tomasz Fujak
2010-01-20  9:11 ` [PATCH v1 1/2] perfevent: Add performance event structure definition and 'extevents' sysfs entry Tomasz Fujak
2010-01-20  9:11 ` [PATCH v1 2/2] [ARM] perfevent: Event description list for ARMv6, Cortex-A8 and Cortex-A9 exported Tomasz Fujak
2010-01-20  9:16 ` [PATCH/RFC v1 0/2] Human readable performance event description in sysfs Peter Zijlstra
2010-01-20  9:46   ` Tomasz Fujak
2010-01-20  9:57   ` Michał Nazarewicz
2010-01-20 13:31     ` Jamie Iles
2010-01-20 13:39       ` Peter Zijlstra [this message]
2010-01-20 13:55         ` Russell King - ARM Linux
2010-01-20 14:01           ` Peter Zijlstra
2010-01-20 14:09             ` Michał Nazarewicz
2010-01-20 14:16               ` Peter Zijlstra
2010-01-20 14:26                 ` Peter Zijlstra
2010-01-20 14:45                   ` Russell King - ARM Linux
2010-01-20 14:54                 ` Michał Nazarewicz
2010-01-20 14:41             ` Russell King - ARM Linux
2010-01-20 15:03               ` Jamie Iles
2010-01-20 15:42                 ` Russell King - ARM Linux
2010-01-20 16:18                   ` Jamie Iles
2010-01-20 16:26               ` Jamie Lokier
2010-01-20 16:35                 ` Russell King - ARM Linux
2010-01-20  9:57 ` Russell King - ARM Linux
2010-01-20 10:21   ` Tomasz Fujak

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=1263994779.4283.1057.camel@laptop \
    --to=peterz@infradead.org \
    --cc=linux-arm-kernel@lists.infradead.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