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: Mon, 12 Aug 2019 20:22:20 +0200 [thread overview]
Message-ID: <E1hxExZ-0000O7-46@stardust.g4.wien.funkfeuer.at> (raw)
In-Reply-To: <CA+E=qVchsqOF_hVD-qBuKwi7PTMYtUR-LE2dD_mpptFJcWE_yw@mail.gmail.com>
Vasily Khoruzhick writes:
> OK, so what should we do? 'perf top'/'perf record' work fine if PMU
> node is dropped, but they don't work if PMU node is present (even with
> interrupts dropped).
Really? Even if you tell it to only listen to software events? (Which
is the only thing you get without a PMU anyway, I believe.)
> I'd prefer to have 'perf top' and 'perf record'
> working instead of 'perf stat'
I think, if a broken PMU confuses 'perf top' beyond usability, it
should be fixed.
Harald
--
Nationalratswahl: Ich trete als unabhängiger Experte für Klimaschutz
und freie Software an! Ich will mit Vorzugsstimmen ins Parlament kommen,
weil wenn ich es nicht mache, kümmert sich womöglich niemand darum.
https://haraldgeyer.at
_______________________________________________
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-12 18:22 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
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 [this message]
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=E1hxExZ-0000O7-46@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).