From: Oliver Upton <oliver.upton@linux.dev>
To: kvmarm@lists.linux.dev, Oliver Upton <oliver.upton@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>, Will Deacon <will@kernel.org>
Subject: Re: (subset) [PATCH 0/3] KVM: arm64: PMU fixes for nVHE, protected mode
Date: Tue, 26 Mar 2024 06:44:42 -0700 [thread overview]
Message-ID: <171145902342.369115.4204778201448709312.b4-ty@linux.dev> (raw)
In-Reply-To: <20240305184840.636212-1-oliver.upton@linux.dev>
On Tue, 05 Mar 2024 18:48:37 +0000, Oliver Upton wrote:
> Series to address a couple of issues I've hit using the nVHE / protected
> mode configuration:
>
> - Host-programmed PMU events that run during guest execution do not
> work if the VM doesn't have a vPMU.
>
> - PMU events do not work at all for non-protected VMs on the
> protected-mode hypervisor
>
> [...]
Just applying the commit that fixes nVHE, I'm happy to ignore the
pKVM issue until the 'real' vCPU context changes appear upstream.
Apologies if this email comes through garbled, I can't access my
usual workstation right now.
Applied to kvmarm/fixes, thanks!
[2/3] KVM: arm64: Fix host-programmed guest events in nVHE
commit: e89c928bedd77d181edc2df01cb6672184775140
--
Best,
Oliver
prev parent reply other threads:[~2024-03-26 13:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 18:48 [PATCH 0/3] KVM: arm64: PMU fixes for nVHE, protected mode Oliver Upton
2024-03-05 18:48 ` [PATCH 1/3] KVM: arm64: pkvm: Actually enable/disable PMU events when running vCPU Oliver Upton
2024-03-06 10:06 ` Marc Zyngier
2024-03-06 10:18 ` Oliver Upton
2024-03-06 13:23 ` Fuad Tabba
2024-03-05 18:48 ` [PATCH 2/3] KVM: arm64: Fix host-programmed guest events in nVHE Oliver Upton
2024-03-06 9:59 ` Marc Zyngier
2024-03-05 18:48 ` [PATCH 3/3] KVM: arm64: Do not disable preemption in kvm_vcpu_pmu_restore_guest() Oliver Upton
2024-03-06 9:52 ` Marc Zyngier
2024-03-06 9:54 ` Oliver Upton
2024-03-26 13:44 ` Oliver Upton [this message]
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=171145902342.369115.4204778201448709312.b4-ty@linux.dev \
--to=oliver.upton@linux.dev \
--cc=james.morse@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=maz@kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
--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 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 read-only IMAP folder(s) and NNTP newsgroup(s).