From: Oliver Upton <oliver.upton@linux.dev>
To: kvmarm@lists.linux.dev
Cc: Marc Zyngier <maz@kernel.org>, James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Reiji Watanabe <reijiw@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Ravi Bangoria <ravi.bangoria@amd.com>,
Nathan Chancellor <nathan@kernel.org>,
mark.rutland@arm.com, Oliver Upton <oliver.upton@linux.dev>
Subject: [PATCH 0/2] KVM: arm64: Fix for probing default PMU
Date: Thu, 25 May 2023 21:27:20 +0000 [thread overview]
Message-ID: <20230525212723.3361524-1-oliver.upton@linux.dev> (raw)
Follow-up to the discussion in [1].
KVM uses a junk perf event to probe for a default PMU instance to use
for the guest, which depends on perf finding the right PMU instance
to use for the event. Looks like perf is going to rely strictly on
the specified PMU type, breaking the entire scheme.
KVM now maintains a list of valid PMU instances that can be selected by
userspace, we can simply walk that to probe for a default PMU.
Applies to 6.4-rc3 and tested on -next.
[1] https://lore.kernel.org/all/20230524214133.GA2359762@dev-arch.thelio-3990X/
Oliver Upton (2):
KVM: arm64: Iterate arm_pmus list to probe for default PMU
KVM: arm64: Document default vPMU behavior on heterogeneous systems
arch/arm64/kvm/pmu-emul.c | 58 ++++++++++++++++-----------------------
1 file changed, 23 insertions(+), 35 deletions(-)
base-commit: 44c026a73be8038f03dbdeef028b642880cf1511
--
2.41.0.rc0.172.g3f132b7071-goog
next reply other threads:[~2023-05-25 21:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 21:27 Oliver Upton [this message]
2023-05-25 21:27 ` [PATCH 1/2] KVM: arm64: Iterate arm_pmus list to probe for default PMU Oliver Upton
2023-05-26 8:41 ` Oliver Upton
2023-05-25 21:27 ` [PATCH 2/2] KVM: arm64: Document default vPMU behavior on heterogeneous systems Oliver Upton
2023-05-31 9:49 ` [PATCH 0/2] KVM: arm64: Fix for probing default PMU 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=20230525212723.3361524-1-oliver.upton@linux.dev \
--to=oliver.upton@linux.dev \
--cc=james.morse@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=nathan@kernel.org \
--cc=peterz@infradead.org \
--cc=ravi.bangoria@amd.com \
--cc=reijiw@google.com \
--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.