From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Simon Horman <horms@verge.net.au>, Magnus Damm <magnus.damm@gmail.com>
Cc: linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/8] ARM: dts: renesas: Add PMU device nodes
Date: Mon, 7 May 2018 15:56:59 +0200 [thread overview]
Message-ID: <1525701427-12914-1-git-send-email-geert+renesas@glider.be> (raw)
Hi Simon, Magnus,
This patch series enables support for the ARM Performance Monitor Units
in Cortex-A7, Cortex-A9, and Cortex-A15 CPU cores on Renesas RZ/A1,
R-Car Gen2, and RZ/G1 SoCs. This allows for better performance analysis
using the "perf" tool.
Sample output of "perf stat echo" on r8a7791/koelsch:
- Before:
Performance counter stats for 'echo':
2,636300 task-clock (msec) # 0,265 CPUs utilized
8 context-switches # 0,003 M/sec
0 cpu-migrations # 0,000 K/sec
43 page-faults # 0,016 M/sec
<not supported> cycles
<not supported> stalled-cycles-frontend
<not supported> stalled-cycles-backend
<not supported> instructions
<not supported> branches
<not supported> branch-misses
0,009960300 seconds time elapsed
- After:
Performance counter stats for 'echo':
2,455400 task-clock (msec) # 0,273 CPUs utilized
3 context-switches # 0,001 M/sec
0 cpu-migrations # 0,000 K/sec
45 page-faults # 0,018 M/sec
3.556.784 cycles # 1,449 GHz
<not supported> stalled-cycles-frontend
<not supported> stalled-cycles-backend
1.350.480 instructions # 0,38 insns per cycle
335.542 branches # 136,655 M/sec
18.075 branch-misses # 5,39% of all branches
0,008987900 seconds time elapsed
Still missing:
- R-Mobile APE6 (no PMU interrupt documented),
- R-Car M1A and H1 (the PMU interrupt seems to be routed to the legacy
SH INTC only?),
- RZ/G1C (SMP support not yet upstream).
This has been tested on r8a7791/koelsch, and boot-tested on
r7s72100/genmai, r8a7790/lager, r8a7792/blanche, and r8a7794/silk.
Thanks!
Geert Uytterhoeven (8):
ARM: dts: r7s72100: Add PMU device node
ARM: dts: r8a7790: Add PMU device nodes
ARM: dts: r8a7791: Add PMU device node
ARM: dts: r8a7792: Add PMU device node
ARM: dts: r8a7793: Add PMU device node
ARM: dts: r8a7794: Add PMU device node
ARM: dts: r8a7743: Add PMU device node
ARM: dts: r8a7745: Add PMU device node
arch/arm/boot/dts/r7s72100.dtsi | 5 +++++
arch/arm/boot/dts/r8a7743.dtsi | 7 +++++++
arch/arm/boot/dts/r8a7745.dtsi | 7 +++++++
arch/arm/boot/dts/r8a7790.dtsi | 18 ++++++++++++++++++
arch/arm/boot/dts/r8a7791.dtsi | 7 +++++++
arch/arm/boot/dts/r8a7792.dtsi | 7 +++++++
arch/arm/boot/dts/r8a7793.dtsi | 7 +++++++
arch/arm/boot/dts/r8a7794.dtsi | 7 +++++++
8 files changed, 65 insertions(+)
--
2.7.4
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next reply other threads:[~2018-05-07 13:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 13:56 Geert Uytterhoeven [this message]
2018-05-07 13:57 ` [PATCH 1/8] ARM: dts: r7s72100: Add PMU device node Geert Uytterhoeven
2018-05-07 13:57 ` [PATCH 2/8] ARM: dts: r8a7790: Add PMU device nodes Geert Uytterhoeven
2018-05-07 13:57 ` [PATCH 3/8] ARM: dts: r8a7791: Add PMU device node Geert Uytterhoeven
2018-05-07 13:57 ` [PATCH 4/8] ARM: dts: r8a7792: " Geert Uytterhoeven
2018-05-07 13:57 ` [PATCH 5/8] ARM: dts: r8a7793: " Geert Uytterhoeven
2018-05-07 13:57 ` [PATCH 6/8] ARM: dts: r8a7794: " Geert Uytterhoeven
2018-05-07 13:57 ` [PATCH 7/8] ARM: dts: r8a7743: " Geert Uytterhoeven
2018-05-07 13:57 ` [PATCH 8/8] ARM: dts: r8a7745: " Geert Uytterhoeven
2018-05-09 14:39 ` [PATCH 0/8] ARM: dts: renesas: Add PMU device nodes Geert Uytterhoeven
2018-05-09 19:12 ` Simon Horman
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=1525701427-12914-1-git-send-email-geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=devicetree@vger.kernel.org \
--cc=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
/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).