linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jean.pihet@newoldbits.com (Jean Pihet)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] ARM: perf: split up perf_event.c by architecture
Date: Tue, 16 Nov 2010 09:32:35 +0100	[thread overview]
Message-ID: <AANLkTikh9k7RmLc_S4FHD+-OnN6aS9d0GPv1gcpjof1A@mail.gmail.com> (raw)
In-Reply-To: <1289842263-21241-1-git-send-email-will.deacon@arm.com>

Will,

On Mon, Nov 15, 2010 at 6:30 PM, Will Deacon <will.deacon@arm.com> wrote:
> Jean - is this a sensible email address to contact you with? Your old
> ? ? ? mvista one has stopped working.
Yes this one is the new one to use.

>
> Our perf_event.c is becoming rather cumbersome as more PMUs are added.
> I know of at least two more (v7-based) PMUs that will be added in the
> coming months which will push this file to the ~4KLOC region.
>
> Since most updates to this file are to do with changes to the generic
> Linux perf API, let's do what x86 does and split out the separate PMU
> implementations into their own files. I've chosen to split it by
> architecture revision: xscale, v6 and v7. Since the v7 PMU registers
> are architected, this means that new v7 implementations just need to
> describe their event mappings.

That makes sense!

>
> Comments welcome.
>
> Cc: Jamie Iles <jamie.iles@picochip.com>
> Cc: Jean Pihet <jean.pihet@newoldbits.com>

Thanks!


>
> Will Deacon (5):
> ?ARM: perf: consolidate common PMU behaviour
> ?ARM: perf: avoid exposing internal stop function for v6 PMU
> ?ARM: perf: add _init() functions to PMUs
> ?ARM: perf: encode PMU name in arm_pmu structure
> ?ARM: perf: separate PMU backends into multiple files
>
> ?arch/arm/kernel/perf_event.c ? ? ? ?| 2448 +----------------------------------
> ?arch/arm/kernel/perf_event_v6.c ? ? | ?674 ++++++++++
> ?arch/arm/kernel/perf_event_v7.c ? ? | ?906 +++++++++++++
> ?arch/arm/kernel/perf_event_xscale.c | ?809 ++++++++++++
> ?4 files changed, 2423 insertions(+), 2414 deletions(-)
> ?create mode 100644 arch/arm/kernel/perf_event_v6.c
> ?create mode 100644 arch/arm/kernel/perf_event_v7.c
> ?create mode 100644 arch/arm/kernel/perf_event_xscale.c
>
>

  parent reply	other threads:[~2010-11-16  8:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-15 17:30 [PATCH 0/5] ARM: perf: split up perf_event.c by architecture Will Deacon
2010-11-15 17:30 ` [PATCH 1/5] ARM: perf: consolidate common PMU behaviour Will Deacon
2010-11-16  8:59   ` Jean Pihet
2010-11-16  9:47     ` Will Deacon
2010-11-16  9:16   ` Jamie Iles
2010-11-15 17:31 ` [PATCH 2/5] ARM: perf: avoid exposing internal stop function for v6 PMU Will Deacon
2010-11-15 19:02   ` Jamie Iles
2010-11-16  9:57     ` Will Deacon
2010-11-15 17:31 ` [PATCH 3/5] ARM: perf: add _init() functions to PMUs Will Deacon
2010-11-16  9:00   ` Jean Pihet
2010-11-16  9:18   ` Jamie Iles
2010-11-15 17:31 ` [PATCH 4/5] ARM: perf: encode PMU name in arm_pmu structure Will Deacon
2010-11-15 19:03   ` Jamie Iles
2010-11-16  8:29     ` Jean Pihet
2010-11-15 17:31 ` [PATCH 5/5] ARM: perf: separate PMU backends into multiple files Will Deacon
2010-11-16  9:11   ` Jean Pihet
2010-11-16 10:12     ` Will Deacon
2010-11-16  8:32 ` Jean Pihet [this message]
2010-11-16  9:38   ` [PATCH 0/5] ARM: perf: split up perf_event.c by architecture Will Deacon

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=AANLkTikh9k7RmLc_S4FHD+-OnN6aS9d0GPv1gcpjof1A@mail.gmail.com \
    --to=jean.pihet@newoldbits.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;
as well as URLs for NNTP newsgroup(s).