public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: jamie.iles@picochip.com (Jamie Iles)
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 16:18:08 +0000	[thread overview]
Message-ID: <20100120161808.GI4089@wear.picochip.com> (raw)
In-Reply-To: <20100120154250.GA27507@n2100.arm.linux.org.uk>

On Wed, Jan 20, 2010 at 03:42:50PM +0000, Russell King - ARM Linux wrote:
> If you're referring to reading the main CPU ID register and relying
> on the part number telling you what CPU you're running on, that's
> unreliable if you're only checking the part number - you at least
> need to check the implementer.
> 
> If you want to do ID checking via the main ID register, there are
> some clashes even if you take the implementer field into account.
Ok, so for the kernel based code I should check the implementer and part
number then. For now we can make sure that the implementor is ARM and add
others if they have compatible PMUs and hope that there aren't any clashes
with nasty side effects.

Jamie

  reply	other threads:[~2010-01-20 16:18 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
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 [this message]
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=20100120161808.GI4089@wear.picochip.com \
    --to=jamie.iles@picochip.com \
    --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