devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maxime Ripard <mripard@kernel.org>
To: Andre Przywara <andre.przywara@arm.com>
Cc: "Chen-Yu Tsai" <wens@csie.org>,
	"Mark Rutland" <mark.rutland@arm.com>,
	"Rob Herring" <robh@kernel.org>,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	"Harald Geyer" <harald@ccbib.org>,
	"Jared D . McNeill" <jmcneill@netbsd.org>,
	"Vasily Khoruzhick" <anarsoul@gmail.com>,
	"Emmanuel Vadot" <manu@freebsd.org>,
	"Clément Péron" <peron.clem@gmail.com>,
	linux-sunxi@googlegroups.com
Subject: Re: [PATCH] arm64: dts: allwinner: a64: Re-add PMU node
Date: Wed, 6 Nov 2019 13:07:54 +0100	[thread overview]
Message-ID: <20191106120754.GC8617@gilmour.lan> (raw)
In-Reply-To: <20191105110651.217513-1-andre.przywara@arm.com>

[-- Attachment #1: Type: text/plain, Size: 1306 bytes --]

Hi,

On Tue, Nov 05, 2019 at 11:06:51AM +0000, Andre Przywara wrote:
> As it was found recently, the Performance Monitoring Unit (PMU) on the
> Allwinner A64 SoC was not generating (the right) interrupts. With the
> SPI numbers from the manual the kernel did not receive any overflow
> interrupts, so perf was not happy at all.
> It turns out that the numbers were just off by 4, so the PMU interrupts
> are from 148 to 151, not from 152 to 155 as the manual describes.
>
> This was found by playing around with U-Boot, which typically does not
> use interrupts, so the GIC is fully available for experimentation:
> With *every* PPI and SPI enabled, an overflowing PMU cycle counter was
> found to set a bit in one of the GICD_ISPENDR registers, with careful
> counting this was determined to be number 148.
>
> Tested with perf record and perf top on a Pine64-LTS. Also tested with
> tasksetting to every core to confirm the assignment between IRQs and
> cores.
>
> This somewhat "revert-fixes" commit ed3e9406bcbc ("arm64: dts: allwinner:
> a64: Drop PMU node").
>
> Fixes: 34a97fcc71c2 ("arm64: dts: allwinner: a64: Add PMU node")
> Fixes: ed3e9406bcbc ("arm64: dts: allwinner: a64: Drop PMU node")
> Signed-off-by: Andre Przywara <andre.przywara@arm.com>

Applied, thanks for figuring this out!
Maxime

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2019-11-06 12:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-05 11:06 [PATCH] arm64: dts: allwinner: a64: Re-add PMU node Andre Przywara
2019-11-06 12:07 ` Maxime Ripard [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=20191106120754.GC8617@gilmour.lan \
    --to=mripard@kernel.org \
    --cc=anarsoul@gmail.com \
    --cc=andre.przywara@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=harald@ccbib.org \
    --cc=jmcneill@netbsd.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-sunxi@googlegroups.com \
    --cc=manu@freebsd.org \
    --cc=mark.rutland@arm.com \
    --cc=peron.clem@gmail.com \
    --cc=robh@kernel.org \
    --cc=wens@csie.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).