From: Harald Geyer <harald@ccbib.org>
To: Vasily Khoruzhick <anarsoul@gmail.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree <devicetree@vger.kernel.org>,
"Jared D . McNeill" <jmcneill@netbsd.org>,
Maxime Ripard <maxime.ripard@bootlin.com>,
Chen-Yu Tsai <wens@csie.org>, Rob Herring <robh+dt@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
arm-linux <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm64: dts: allwinner: a64: Drop PMU node
Date: Tue, 06 Aug 2019 22:19:25 +0200 [thread overview]
Message-ID: <E1hv5vZ-0000jN-M8@stardust.g4.wien.funkfeuer.at> (raw)
In-Reply-To: <CA+E=qVfh7mirJhRsDTeuAVgG55ia936uFSFVKR0N5Pn4GCF1UA@mail.gmail.com>
Vasily Khoruzhick writes:
> On Tue, Aug 6, 2019 at 7:35 AM Robin Murphy <robin.murphy@arm.com> wrote:
> >
> > On 06/08/2019 15:01, Vasily Khoruzhick wrote:
> > > Looks like PMU in A64 is broken, it generates no interrupts at all and
> > > as result 'perf top' shows no events.
> >
> > Does something like 'perf stat sleep 1' at least count cycles correctly?
> > It could well just be that the interrupt numbers are wrong...
>
> Looks like it does, at least result looks plausible:
I'm using perf stat regularly (cache benchmarks) and it works fine.
Unfortunately I wasn't aware that perf stat is a poor test for
the interrupts part of the node, when I added it. So I'm not too
surprised I got it wrong.
However, it would be unfortunate if the node got removed completely,
because perf stat would not work anymore. Maybe we can only remove
the interrupts or just fix them even if the HW doesn't work?
Harald
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-08-06 20:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 14:01 [PATCH] arm64: dts: allwinner: a64: Drop PMU node Vasily Khoruzhick
2019-08-06 14:35 ` Robin Murphy
2019-08-06 14:45 ` Vasily Khoruzhick
2019-08-06 20:19 ` Harald Geyer [this message]
2019-08-06 20:52 ` Vasily Khoruzhick
2019-08-06 21:14 ` Robin Murphy
2019-08-07 2:39 ` Vasily Khoruzhick
2019-08-07 11:56 ` Maxime Ripard
2019-08-07 17:36 ` Vasily Khoruzhick
2019-08-08 16:26 ` Maxime Ripard
2019-08-08 19:59 ` Vasily Khoruzhick
2019-08-12 8:04 ` Maxime Ripard
2019-08-12 18:01 ` Vasily Khoruzhick
2019-08-12 18:22 ` Harald Geyer
2019-08-13 5:39 ` Maxime Ripard
2019-09-23 23:51 ` Vasily Khoruzhick
2019-09-23 23:55 ` Vasily Khoruzhick
2019-09-25 11:08 ` Maxime Ripard
2019-10-31 19:10 ` Clément Péron
2019-10-31 20:35 ` Vasily Khoruzhick
2019-11-01 11:30 ` Clément Péron
2019-11-01 15:47 ` Andre Przywara
2019-11-11 1:43 ` André Przywara
2019-08-07 11:59 ` Robin Murphy
2019-08-07 11:12 ` Mark Rutland
2019-08-06 19:10 ` Emmanuel Vadot
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=E1hv5vZ-0000jN-M8@stardust.g4.wien.funkfeuer.at \
--to=harald@ccbib.org \
--cc=anarsoul@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jmcneill@netbsd.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@bootlin.com \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--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).