From: mingo@elte.hu (Ingo Molnar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] arm/perfevents: implement perf event support for ARMv6
Date: Fri, 11 Dec 2009 11:19:52 +0100 [thread overview]
Message-ID: <20091211101952.GA16882@elte.hu> (raw)
In-Reply-To: <1260524662-30683-5-git-send-email-jamie.iles@picochip.com>
* Jamie Iles <jamie.iles@picochip.com> wrote:
> This patch implements support for ARMv6 performance counters in the
> Linux performance events subsystem. ARMv6 architectures that have the
> performance counters should enable ARMV6_PERF_EVENTS and define the
> interrupts for the counters in arch/arm/kernel/perf_event.c
>
> Signed-off-by: Jamie Iles <jamie.iles@picochip.com>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Ingo Molnar <mingo@elte.hu>
> ---
> arch/arm/Kconfig | 5 +
> arch/arm/include/asm/perf_event.h | 2 -
> arch/arm/kernel/Makefile | 1 +
> arch/arm/kernel/perf_event.c | 993 +++++++++++++++++++++++++++++++++++++
> 4 files changed, 999 insertions(+), 2 deletions(-)
> create mode 100644 arch/arm/kernel/perf_event.c
Very nice!
The code looks sane - i've only got a few (minor) stylistic comments.
Firstly, you seem to be using several different, inconsistent multi-line
comment styles:
> + /*
> + * The interrupts are cleared by writing the overflow flags back to
> + * the control register. All of the other bits don't have any effect
> + * if they are rewritten, so write the whole value back.
> + */
> +/* Define the IRQs for the system. We could use something like a platform
> + * device but that seems fairly heavyweight for this. Also, the performance
> + * counters can't be removed or hotplugged. */
please use the first variant everywhere, that's what is specified in
Documentation/CodingStyle as well:
/*
* Comment .....
* ...... goes here.
*/
There's also some whitespace damage as well:
> + /* frame pointers should strictly progress back up the stack
> + * (towards higher addresses) */
(should be tabs, not spaces)
Thanks,
Ingo
prev parent reply other threads:[~2009-12-11 10:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 9:44 perf events for ARMv6 Jamie Iles
2009-12-11 9:44 ` [PATCH 1/4] arm: provide a mechanism to reserve performance counters Jamie Iles
2009-12-11 9:44 ` [PATCH 2/4] arm/oprofile: reserve the PMU when starting Jamie Iles
2009-12-11 9:44 ` [PATCH 3/4] arm: enable support for software perf events Jamie Iles
2009-12-11 9:44 ` [PATCH 4/4] arm/perfevents: implement perf event support for ARMv6 Jamie Iles
2009-12-11 10:19 ` Ingo Molnar [this message]
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=20091211101952.GA16882@elte.hu \
--to=mingo@elte.hu \
--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).