From: Marc Zyngier <maz@kernel.org>
To: linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org
Cc: Mark Rutland <mark.rutland@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Eric Auger <eric.auger@redhat.com>,
James Morse <james.morse@arm.com>,
Robin Murphy <robin.murphy@arm.com>,
Julien Thierry <julien.thierry.kdev@gmail.com>
Subject: [PATCH v2 0/2] KVM: arm64: Filtering PMU events
Date: Mon, 9 Mar 2020 12:48:35 +0000 [thread overview]
Message-ID: <20200309124837.19908-1-maz@kernel.org> (raw)
It is at times necessary to prevent a guest from being able to sample
certain events if multiple CPUs share resources such as a cache level. In
this case, it would be interesting if the VMM could simply prevent certain
events from being counted instead of hiding the PMU.
Given that most events are not architected, there is no easy way to
designate which events shouldn't be counted other than specifying the raw
event number.
Since I have no idea whether it is better to use an event whitelist or
blacklist, the proposed API takes a cue from the x86 version and allows
either allowing or denying counting of ranges of events. The event space
being pretty large (16bits on ARMv8.1), the default policy is set by the
first filter that gets installed (default deny if we first allow, default
allow if we first deny).
The filter state is global to the guest, despite the PMU being per CPU. I'm
not sure whether it would be worth it making it CPU-private.
As an example of what can be done in userspace, I have the corresponding
kvmtool hack here[1].
* From v1:
- Cleaned up handling of the cycle counter
- Documented restrictions on SW_INC, CHAIN and CPU_CYCLES events
[1] https://git.kernel.org/pub/scm/linux/kernel/git/maz/kvmtool.git/commit/?h=pmu-filter
Marc Zyngier (2):
KVM: arm64: Add PMU event filtering infrastructure
KVM: arm64: Document PMU filtering API
Documentation/virt/kvm/devices/vcpu.rst | 40 ++++++++++++
arch/arm64/include/asm/kvm_host.h | 6 ++
arch/arm64/include/uapi/asm/kvm.h | 16 +++++
virt/kvm/arm/arm.c | 2 +
virt/kvm/arm/pmu.c | 84 ++++++++++++++++++++-----
5 files changed, 132 insertions(+), 16 deletions(-)
--
2.20.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-03-09 12:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 12:48 Marc Zyngier [this message]
2020-03-09 12:48 ` [PATCH v2 1/2] KVM: arm64: Add PMU event filtering infrastructure Marc Zyngier
2020-03-09 18:05 ` Auger Eric
2020-03-10 11:03 ` Marc Zyngier
2020-03-10 17:40 ` Auger Eric
2020-03-10 18:00 ` Marc Zyngier
2020-03-10 18:26 ` Auger Eric
2020-08-18 23:24 ` Alexander Graf
2020-08-20 7:37 ` Marc Zyngier
2020-09-02 12:23 ` Alexander Graf
2020-03-09 12:48 ` [PATCH v2 2/2] KVM: arm64: Document PMU filtering API Marc Zyngier
2020-03-09 18:17 ` Auger Eric
2020-03-10 11:54 ` Marc Zyngier
2020-03-10 17:30 ` Auger Eric
2020-03-10 18:07 ` 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=20200309124837.19908-1-maz@kernel.org \
--to=maz@kernel.org \
--cc=eric.auger@redhat.com \
--cc=james.morse@arm.com \
--cc=julien.thierry.kdev@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robin.murphy@arm.com \
--cc=suzuki.poulose@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;
as well as URLs for NNTP newsgroup(s).