All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Wahren <stefan.wahren@i2se.com>
To: Marc Zyngier <marc.zyngier@arm.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Vince Weaver <vincent.weaver@maine.edu>
Cc: Ingo Molnar <mingo@redhat.com>,
	linux-rpi-kernel@lists.infradead.org,
	Eric Anholt <eric@anholt.net>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	bcm-kernel-feedback-list@broadcom.com,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm: bcm2835: Add the PMU to the devicetree.
Date: Fri, 18 May 2018 11:37:38 +0200 (CEST)	[thread overview]
Message-ID: <1863838560.56771.1526636258081@email.1und1.de> (raw)
In-Reply-To: <d6b6f632-2051-a239-3e44-4750f2ac89d5@arm.com>

Hi Marc,

> Marc Zyngier <marc.zyngier@arm.com> hat am 18. Mai 2018 um 10:07 geschrieben:
> 
> I have a pretty simple series[1] which I used to profile 32bit guests on
> an arm64 KVM host. Nobody really cared about it because running a 32bit
> kernel on 64bit HW is a bit odd, to say the least, and I'm probably the
> only one actually running 32bit VMs.
> 
> > 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...
> Ah, so you're *really* doing that? I'm not going to ask why, I'm scared
> of the answer... ;-)
> 
> Anyway, I can repost that series if that will prevent people from having
> that kind of silly hacks.

yes please. But there is a minor nit: some patches introduce new files without SPDX tags.

Thanks
Stefan

> 
> Thanks,
> 
> 	M.
> 
> [1]
> https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git/log/?h=kvm-arm/pmuv3-32bit
> -- 
> Jazz is not dead. It just smells funny...

WARNING: multiple messages have this Message-ID (diff)
From: stefan.wahren@i2se.com (Stefan Wahren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: bcm2835: Add the PMU to the devicetree.
Date: Fri, 18 May 2018 11:37:38 +0200 (CEST)	[thread overview]
Message-ID: <1863838560.56771.1526636258081@email.1und1.de> (raw)
In-Reply-To: <d6b6f632-2051-a239-3e44-4750f2ac89d5@arm.com>

Hi Marc,

> Marc Zyngier <marc.zyngier@arm.com> hat am 18. Mai 2018 um 10:07 geschrieben:
> 
> I have a pretty simple series[1] which I used to profile 32bit guests on
> an arm64 KVM host. Nobody really cared about it because running a 32bit
> kernel on 64bit HW is a bit odd, to say the least, and I'm probably the
> only one actually running 32bit VMs.
> 
> > 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...
> Ah, so you're *really* doing that? I'm not going to ask why, I'm scared
> of the answer... ;-)
> 
> Anyway, I can repost that series if that will prevent people from having
> that kind of silly hacks.

yes please. But there is a minor nit: some patches introduce new files without SPDX tags.

Thanks
Stefan

> 
> Thanks,
> 
> 	M.
> 
> [1]
> https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git/log/?h=kvm-arm/pmuv3-32bit
> -- 
> Jazz is not dead. It just smells funny...

  reply	other threads:[~2018-05-18  9:38 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-17 13:17 [PATCH] arm: bcm2835: Add the PMU to the devicetree Eric Anholt
2018-05-17 13:17 ` Eric Anholt
2018-05-17 14:11 ` Vince Weaver
2018-05-17 14:11   ` Vince Weaver
2018-05-17 14:30   ` Eric Anholt
2018-05-17 14:30     ` Eric Anholt
2018-05-17 16:02     ` Vince Weaver
2018-05-17 16:02       ` Vince Weaver
2018-05-17 16:06   ` Stefan Wahren
2018-05-17 16:06     ` Stefan Wahren
2018-05-17 15:59 ` Stefan Wahren
2018-05-17 15:59   ` Stefan Wahren
2018-05-17 16:34   ` Vince Weaver
2018-05-17 16:34     ` Vince Weaver
2018-05-17 16:55     ` Stefan Wahren
2018-05-17 16:55       ` Stefan Wahren
2018-05-17 18:07       ` Peter Zijlstra
2018-05-17 18:07         ` Peter Zijlstra
2018-05-17 18:27         ` Vince Weaver
2018-05-17 18:27           ` Vince Weaver
2018-05-17 19:31           ` Vince Weaver
2018-05-17 19:31             ` Vince Weaver
2018-05-17 19:59             ` Florian Fainelli
2018-05-17 19:59               ` Florian Fainelli
2018-05-18  8:07               ` Marc Zyngier
2018-05-18  8:07                 ` Marc Zyngier
2018-05-18  9:37                 ` Stefan Wahren [this message]
2018-05-18  9:37                   ` Stefan Wahren
2018-05-18  9:49                   ` Marc Zyngier
2018-05-18  9:49                     ` Marc Zyngier
2018-05-17 17:09     ` Eric Anholt
2018-05-17 17:09       ` Eric Anholt
2018-05-17 16:44 ` Peter Robinson
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=1863838560.56771.1526636258081@email.1und1.de \
    --to=stefan.wahren@i2se.com \
    --cc=acme@kernel.org \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=eric@anholt.net \
    --cc=f.fainelli@gmail.com \
    --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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.