From: Florian Fainelli <f.fainelli@gmail.com>
To: Vince Weaver <vincent.weaver@maine.edu>,
Peter Zijlstra <peterz@infradead.org>,
marc.zyngier@arm.com
Cc: Stefan Wahren <stefan.wahren@i2se.com>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
linux-rpi-kernel@lists.infradead.org,
bcm-kernel-feedback-list@broadcom.com,
linux-kernel@vger.kernel.org, Eric Anholt <eric@anholt.net>,
linux-arm-kernel@lists.infradead.org,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH] arm: bcm2835: Add the PMU to the devicetree.
Date: Thu, 17 May 2018 12:59:28 -0700 [thread overview]
Message-ID: <0a643984-1586-8c56-6627-430f0c2a4ba8@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1805171530080.8529@macbook-air>
On 05/17/2018 12:31 PM, Vince Weaver wrote:
> On Thu, 17 May 2018, Vince Weaver wrote:
>
>> On Thu, 17 May 2018, Peter Zijlstra wrote:
>> with cortex-a7 now, would it be possible to later drop that if proper
>> cortex-a53 support is added to the armv7 pmu driver? Or would that lead
>> to all kinds of back-compatability mess?
>
> For what it's worth, the pi-foundation kernel bcm2710 device tree file
> does:
>
> arm-pmu {
> #ifdef RPI364
> compatible = "arm,armv8-pmuv3", "arm,cortex-a7-pmu";
> #else
> compatible = "arm,cortex-a7-pmu";
> #endif
> interrupt-parent = <&local_intc>;
> interrupts = <9>;
> };
>
>
> Which is probably where I was getting the arm,armv8-pmuv3 from in my
> original patch.
I thought somehow that Marc Z. had unified
arch/arm/kernel/perf_event_v7.c and arch/arm64/kernel/perf_event.c into
a common driver entry point under drivers/perf/arm_pmu.c but I don't see
it and after about 15 minutes looking at it, it does not look as trivial
as I though to separate out those files so the ARMv8 PMU description can
be moved into a generic location for instance.
FWIW, Broadcom STB chips, even when 64-bit capable or often used with an
32-bit ARM kernel, so having the ARMv8 PMUs work under a 32-bit ARM
kernel would be great. The downstream solution we have sued thus far is
to find the closest compatible string to represent those, which is not
great...
--
Florian
next prev parent reply other threads:[~2018-05-17 19:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 13:17 Eric Anholt
2018-05-17 14:11 ` Vince Weaver
2018-05-17 14:30 ` Eric Anholt
2018-05-17 16:02 ` Vince Weaver
2018-05-17 16:06 ` Stefan Wahren
2018-05-17 15:59 ` Stefan Wahren
2018-05-17 16:34 ` Vince Weaver
2018-05-17 16:55 ` Stefan Wahren
2018-05-17 18:07 ` Peter Zijlstra
2018-05-17 18:27 ` Vince Weaver
2018-05-17 19:31 ` Vince Weaver
2018-05-17 19:59 ` Florian Fainelli [this message]
2018-05-18 8:07 ` Marc Zyngier
2018-05-18 9:37 ` Stefan Wahren
2018-05-18 9:49 ` Marc Zyngier
2018-05-17 17:09 ` Eric Anholt
2018-05-17 16:44 ` Peter Robinson
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=0a643984-1586-8c56-6627-430f0c2a4ba8@gmail.com \
--to=f.fainelli@gmail.com \
--cc=acme@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=eric@anholt.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=stefan.wahren@i2se.com \
--cc=vincent.weaver@maine.edu \
/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
all inboxes | Powered by JetHome®