From: Fuad Tabba <tabba@google.com>
To: kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org
Cc: maz@kernel.org, oliver.upton@linux.dev, mark.rutland@arm.com,
will@kernel.org, joey.gouly@arm.com, suzuki.poulose@arm.com,
yuzenghui@huawei.com, catalin.marinas@arm.com,
broonie@kernel.org, qperret@google.com, vdonnefort@google.com,
tabba@google.com
Subject: [PATCH v1 0/3] KVM: arm64: Fix initializing HCRX_EL2 and other traps in pKVM
Date: Fri, 14 Feb 2025 15:02:55 +0000 [thread overview]
Message-ID: <20250214150258.464798-1-tabba@google.com> (raw)
Since the introduction of initializing and setting HCRX_EL2 traps
in KVM, we haven't updated the pKVM code upstream do the same for
the hyp view.
Additionally, the current behavior of pKVM is to initialize the
hyp view of the vm and of _all_ its vcpus when the _first_ vcpu
is run. However, with the introduction of kvm_calculate_traps()
[*], some of the host trap values are not calculated until the
corresponding vcpu is run for the first time. This causes pKVM to
get the wrong view of some of the system registers, e.g.,
HCRX_EL2, for vcpus other than the first run vcpu, since it uses
the host's version as a starting point --- particularly for
non-protected vms. Because of these issues, it's might not be
possible to run a non-protected VM when certain features (e.g.,
MOPS) are supported by the system.
This series initializes HCRX_EL2 for VMs in protected mode. It
also initializes the hyp view of each vcpu after its
corresponding host vcpu has been fully initialized, i.e., run for
the first time.
This series is based on Linux 6.14-rc2.
Cheers,
/fuad
[*] Commit f1ff3fc5209a ("KVM: arm64: unify code to prepare traps")
Fuad Tabba (3):
KVM: arm64: Initialize HCRX_EL2 traps in pKVM
KVM: arm64: Factor out pkvm hyp vcpu creation to separate function
KVM: arm64: Create each pKVM hyp vcpu after its corresponding host
vcpu
arch/arm64/include/asm/kvm_host.h | 2 +
arch/arm64/include/asm/kvm_pkvm.h | 1 +
arch/arm64/kvm/arm.c | 4 +
arch/arm64/kvm/hyp/include/nvhe/pkvm.h | 6 --
arch/arm64/kvm/hyp/nvhe/pkvm.c | 100 +++++++++++++++++++------
arch/arm64/kvm/pkvm.c | 70 +++++++++--------
6 files changed, 118 insertions(+), 65 deletions(-)
base-commit: a64dcfb451e254085a7daee5fe51bf22959d52d3
--
2.48.1.601.g30ceb7b040-goog
next reply other threads:[~2025-02-14 15:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 15:02 Fuad Tabba [this message]
2025-02-14 15:02 ` [PATCH v1 1/3] KVM: arm64: Initialize HCRX_EL2 traps in pKVM Fuad Tabba
2025-02-26 10:07 ` Oliver Upton
2025-02-26 10:45 ` Marc Zyngier
2025-02-26 12:44 ` Fuad Tabba
2025-02-26 15:28 ` Marc Zyngier
2025-02-26 18:53 ` Oliver Upton
2025-02-26 18:54 ` Fuad Tabba
2025-02-26 12:36 ` Fuad Tabba
2025-02-14 15:02 ` [PATCH v1 2/3] KVM: arm64: Factor out pkvm hyp vcpu creation to separate function Fuad Tabba
2025-02-14 15:02 ` [PATCH v1 3/3] KVM: arm64: Create each pKVM hyp vcpu after its corresponding host vcpu Fuad Tabba
2025-02-17 15:30 ` Will Deacon
2025-02-17 15:41 ` Fuad Tabba
2025-02-17 15:56 ` Fuad Tabba
2025-02-18 9:27 ` Will Deacon
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=20250214150258.464798-1-tabba@google.com \
--to=tabba@google.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=qperret@google.com \
--cc=suzuki.poulose@arm.com \
--cc=vdonnefort@google.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 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.