From: Qian Cai <qcai@redhat•com>
To: Marc Zyngier <maz@kernel•org>
Cc: linux-arm-kernel@lists•infradead.org,
kvmarm@lists•cs.columbia.edu, kernel-team@android•com,
Stephen Rothwell <sfr@canb•auug.org.au>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Alexandru Elisei <alexandru.elisei@arm•com>
Subject: Re: [PATCH] KVM: arm64: Don't access PMCR_EL0 when no PMU is available
Date: Mon, 04 Jan 2021 13:42:31 -0500 [thread overview]
Message-ID: <22cd2b3e8b8b278f110a3540755583efee7189fd.camel@redhat.com> (raw)
In-Reply-To: <f7b97771ed29c7630f678a8939a591dd@kernel.org>
On Mon, 2021-01-04 at 18:26 +0000, Marc Zyngier wrote:
> What I'm suggesting is this [1], which is to get rid of KVM_ARM_PMU
> completely. At least, the kernel configuration will be consistent.
>
Do you have a patch for CONFIG_KVM to select HW_PERF_EVENTS then? I could cook
one if not.
> Overall, I think there is an issue with KVM exposing more than it
> should to userspace when no PMU is defined, but I don't think that's
> the problem you are seeing.
>
> M.
>
> [1] https://lore.kernel.org/r/20210104172723.2014324-1-maz@kernel.org
next prev parent reply other threads:[~2021-01-04 18:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201210083059.1277162-1-maz@kernel.org>
2021-01-04 15:47 ` [PATCH] KVM: arm64: Don't access PMCR_EL0 when no PMU is available Qian Cai
2021-01-04 16:08 ` Marc Zyngier
2021-01-04 16:22 ` Qian Cai
2021-01-04 16:27 ` Marc Zyngier
2021-01-04 18:20 ` Qian Cai
2021-01-04 18:26 ` Marc Zyngier
2021-01-04 18:42 ` Qian Cai [this message]
2021-01-04 19:32 ` Marc Zyngier
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=22cd2b3e8b8b278f110a3540755583efee7189fd.camel@redhat.com \
--to=qcai@redhat$(echo .)com \
--cc=alexandru.elisei@arm$(echo .)com \
--cc=kernel-team@android$(echo .)com \
--cc=kvmarm@lists$(echo .)cs.columbia.edu \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=maz@kernel$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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