From: Marc Zyngier <marc.zyngier@arm.com>
To: "Leeder\, Neil" <nleeder@codeaurora.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Mark Langsdorf <mlangsdo@redhat.com>,
Mark Salter <msalter@redhat.com>, Jon Masters <jcm@redhat.com>,
Timur Tabi <timur@codeaurora.org>,
Jeremy Linton <jeremy.linton@arm.com>
Subject: Re: [PATCH/RFC] arm64: pmu: add Qualcomm Technologies extensions
Date: Fri, 03 Mar 2017 10:17:28 +0000 [thread overview]
Message-ID: <8737eu4qbr.fsf@on-the-bus.cambridge.arm.com> (raw)
In-Reply-To: <2c6fcb54-482a-14dc-0fbb-58df0f9a68b5@codeaurora.org> (Neil Leeder's message of "Thu, 2 Mar 2017 14:30:53 -0500")
On Thu, Mar 02 2017 at 7:30:53 pm GMT, "Leeder, Neil" <nleeder@codeaurora.org> wrote:
> Hi Mark Z.,
>
> On 3/2/2017 4:05 AM, Marc Zyngier wrote:
>> On 01/03/17 21:36, Leeder, Neil wrote:
>>> On 3/1/2017 1:10 PM, Mark Rutland wrote:
>>>> KVM already has (architected) PMU support, and without a corresponding
>>>> KVM patch this is at best insufficient. I don't imagine the KVM folk
>>>> will be too thrilled about the prospect of emulating an IMPLEMENTATION
>>>> DEFINED CPU feature like this.
>>>
>>> Does KVM handle ARMv7 PMU implementations? If so, do you know what it
>>> does for the scorpion_* and krait_* implementations in
>>> arch/arm/kernel/perf_events_v7.c? These extensions in ARMv8 are very
>>> similar to the krait extensions, with some 64-bit tweaks, so could be
>>> handled by KVM the same way it handles the ARMv7 cases.
>>
>> No, KVM doesn't handle the ARMv7 PMU at all. I'm not aware of the
>> virtualization extensions being available on Scorpion or Krait, which
>> makes it a moot point. What it handles is the PMUv3 architecture.
>
> Thank you for the explanation.
>
> This driver is specifically for Qualcomm Technologies server
> chips. They will not be in a heterogenous environment with
> non-Qualcomm processors, so there should be no migration issues.
How do you know that? I'm afraid this is not something you or I can
guarantee (and even less enforce).
> If we were to provide a patch which added KVM support for the 4
> additional registers here, would you consider reviewing it, or is
> adding implementation-defined registers a show-stopper?
At the moment, it seems that there is a consensus against adding support
for an IMPDEF PMU.
Thanks,
M.
--
Jazz is not dead, it just smell funny.
next prev parent reply other threads:[~2017-03-03 10:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 16:18 [PATCH/RFC] arm64: pmu: add Qualcomm Technologies extensions Neil Leeder
2017-03-01 18:10 ` Mark Rutland
2017-03-01 19:48 ` Marc Zyngier
2017-03-01 21:36 ` Leeder, Neil
2017-03-02 9:05 ` Marc Zyngier
2017-03-02 19:30 ` Leeder, Neil
2017-03-03 10:17 ` Marc Zyngier [this message]
2017-03-02 15:16 ` Mark Rutland
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=8737eu4qbr.fsf@on-the-bus.cambridge.arm.com \
--to=marc.zyngier@arm.com \
--cc=catalin.marinas@arm.com \
--cc=jcm@redhat.com \
--cc=jeremy.linton@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=mlangsdo@redhat.com \
--cc=msalter@redhat.com \
--cc=nleeder@codeaurora.org \
--cc=peterz@infradead.org \
--cc=timur@codeaurora.org \
--cc=will.deacon@arm.com \
/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