From: Quentin Perret <qperret@google.com>
To: Marc Zyngier <maz@kernel.org>,
Oliver Upton <oliver.upton@linux.dev>,
Joey Gouly <joey.gouly@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>
Cc: Quentin Perret <qperret@google.com>,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/4] Selftest for pKVM ownership transitions
Date: Wed, 16 Apr 2025 16:08:56 +0000 [thread overview]
Message-ID: <20250416160900.3078417-1-qperret@google.com> (raw)
Hi all,
This is the v3 of the pKVM selftest series, v2 was here [1]. This series
depends on [2] which moves the hyp tracking to the vmemmap. A full
stack on top of v6.15-rc2 with everything applied is available here:
https://android-kvm.googlesource.com/linux qperret/pkvm-selftest-v3
Changes since v2:
- rebased on top of v2 of the hyp-state-in-vmemmap series [2];
- thanks to above rebase, dropped the PKVM_SELFTEST kconfig option and
folded the selftest under the existing NVHE_EL2_DEBUG;
- fixed commit message of patch 02
Changes since v1:
- added support for testing NP guest transitions;
- added .data section in pKVM to allow using non-zero globals (needed
for previous point);
- dropped superfluous WARN() from __pkvm_host_share_guest() which is a
pain for testing;
- updated assertions for hyp/host transitions according to the
discussion on v1.
[1] https://lore.kernel.org/kvmarm/20250225015327.3708420-1-qperret@google.com/
[2] https://lore.kernel.org/kvmarm/20250416152648.2982950-1-qperret@google.com/
Thanks,
Quentin
David Brazdil (1):
KVM: arm64: Add .hyp.data section
Quentin Perret (3):
KVM: arm64: Don't WARN from __pkvm_host_share_guest()
KVM: arm64: Selftest for pKVM transitions
KVM: arm64: Extend pKVM selftest for np-guests
arch/arm64/include/asm/kvm_pkvm.h | 6 +
arch/arm64/include/asm/sections.h | 1 +
arch/arm64/kernel/image-vars.h | 2 +
arch/arm64/kernel/vmlinux.lds.S | 18 +-
arch/arm64/kvm/arm.c | 7 +
arch/arm64/kvm/hyp/include/nvhe/mem_protect.h | 6 +
arch/arm64/kvm/hyp/nvhe/hyp.lds.S | 2 +
arch/arm64/kvm/hyp/nvhe/mem_protect.c | 198 +++++++++++++++++-
arch/arm64/kvm/hyp/nvhe/setup.c | 12 ++
arch/arm64/kvm/pkvm.c | 2 +
10 files changed, 250 insertions(+), 4 deletions(-)
--
2.49.0.604.gff1f9ca942-goog
next reply other threads:[~2025-04-16 16:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 16:08 Quentin Perret [this message]
2025-04-16 16:08 ` [PATCH v3 1/4] KVM: arm64: Add .hyp.data section Quentin Perret
2025-04-16 16:08 ` [PATCH v3 2/4] KVM: arm64: Don't WARN from __pkvm_host_share_guest() Quentin Perret
2025-04-16 16:08 ` [PATCH v3 3/4] KVM: arm64: Selftest for pKVM transitions Quentin Perret
2025-04-16 16:09 ` [PATCH v3 4/4] KVM: arm64: Extend pKVM selftest for np-guests Quentin Perret
2025-05-06 9:07 ` [PATCH v3 0/4] Selftest for pKVM ownership transitions 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=20250416160900.3078417-1-qperret@google.com \
--to=qperret@google.com \
--cc=catalin.marinas@arm.com \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--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
all inboxes | Powered by JetHome®