From: Oliver Upton <oliver.upton@linux.dev>
To: kvmarm@lists.linux.dev
Cc: kvm@vger.kernel.org, Marc Zyngier <maz@kernel.org>,
James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Oliver Upton <oliver.upton@linux.dev>
Subject: [PATCH v2 0/2] KVM: arm64: PMU event filtering fixes
Date: Fri, 13 Oct 2023 05:28:59 +0000 [thread overview]
Message-ID: <20231013052901.170138-1-oliver.upton@linux.dev> (raw)
Set of fixes to KVM's handling of the exception level event filtering in
the PMU event type registers.
I dropped the PMU+NV disablement this time around as we need a complete
fix for that problem. At the same time, I want to get a rework of our
sysreg masks upstream soon to avoid any negative interaction with new
PMU features going in on the driver side of things.
Additionally, I added a fix for the non-secure filtering bits that
Suzuki had spotted (thanks!)
Oliver Upton (2):
KVM: arm64: Treat PMEVTYPER<n>_EL0.NSH as RES0
KVM: arm64: Virtualise PMEVTYPER<n>_EL1.{NSU,NSK}
arch/arm64/kvm/pmu-emul.c | 26 +++++++++++++++++---------
arch/arm64/kvm/sys_regs.c | 8 ++++++--
include/kvm/arm_pmu.h | 5 +++++
include/linux/perf/arm_pmuv3.h | 8 +++++---
4 files changed, 33 insertions(+), 14 deletions(-)
base-commit: 6465e260f48790807eef06b583b38ca9789b6072
--
2.42.0.655.g421f12c284-goog
next reply other threads:[~2023-10-13 5:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 5:28 Oliver Upton [this message]
2023-10-13 5:29 ` [PATCH v2 1/2] KVM: arm64: Treat PMEVTYPER<n>_EL0.NSH as RES0 Oliver Upton
2023-10-13 5:29 ` [PATCH v2 2/2] KVM: arm64: Virtualise PMEVTYPER<n>_EL1.{NSU,NSK} Oliver Upton
2023-10-13 5:56 ` Oliver Upton
2023-10-18 13:31 ` Marc Zyngier
2023-10-18 18:24 ` Oliver Upton
2023-10-19 7:20 ` Marc Zyngier
2023-10-16 12:47 ` [PATCH v2 0/2] KVM: arm64: PMU event filtering fixes Suzuki K Poulose
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=20231013052901.170138-1-oliver.upton@linux.dev \
--to=oliver.upton@linux.dev \
--cc=james.morse@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=maz@kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=yuzenghui@huawei.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 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.