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: Vincent Donnefort <vdonnefort@google.com>,
Quentin Perret <qperret@google.com>,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/6] Move pKVM ownership state to hyp_vmemmap
Date: Thu, 27 Feb 2025 00:33:04 +0000 [thread overview]
Message-ID: <20250227003310.367350-1-qperret@google.com> (raw)
Hi all,
This series moves the hypervisor's ownership state to the hyp_vmemmap,
as discussed in [1]. The two main benefits are:
1. much cheaper hyp state lookups, since we can avoid the hyp stage-1
page-table walk;
2. de-correlates the hyp state from the presence of a mapping in the
linear map range of the hypervisor; which enables a bunch of
clean-ups in the existing code and will simplify the introduction of
other features in the future (hyp tracing, ...)
Patch 01 is a self-sufficient cleanup that I found thanks to patch 05.
Patches 02-04 implement the aforementioned migration of the hyp state
to the vmemmap. Patches 05 and 06 are cleanups enabled by that
migration.
Patches based on 6.14-rc4, tested on Qemu.
Thanks!
Quentin
[1] https://lore.kernel.org/kvmarm/Z79ZJVOHtNu6YsVt@google.com/
Fuad Tabba (1):
KVM: arm64: Track SVE state in the hypervisor vcpu structure
Quentin Perret (5):
KVM: arm64: Use 0b11 for encoding PKVM_NOPAGE
KVM: arm64: Introduce {get,set}_host_state() helpers
KVM: arm64: Move hyp state to hyp_vmemmap
KVM: arm64: Defer EL2 stage-1 mapping on share
KVM: arm64: Unconditionally cross check hyp state
arch/arm64/include/asm/kvm_host.h | 12 +--
arch/arm64/kvm/hyp/include/nvhe/memory.h | 35 ++++++--
arch/arm64/kvm/hyp/nvhe/hyp-main.c | 4 -
arch/arm64/kvm/hyp/nvhe/mem_protect.c | 106 ++++++++++++-----------
arch/arm64/kvm/hyp/nvhe/pkvm.c | 54 ++++++++++--
arch/arm64/kvm/hyp/nvhe/setup.c | 10 ++-
6 files changed, 147 insertions(+), 74 deletions(-)
--
2.48.1.658.g4767266eb4-goog
next reply other threads:[~2025-02-27 0:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 0:33 Quentin Perret [this message]
2025-02-27 0:33 ` [PATCH 1/6] KVM: arm64: Track SVE state in the hypervisor vcpu structure Quentin Perret
2025-02-27 0:33 ` [PATCH 2/6] KVM: arm64: Use 0b11 for encoding PKVM_NOPAGE Quentin Perret
2025-03-14 11:07 ` Marc Zyngier
2025-03-14 14:13 ` Quentin Perret
2025-03-16 11:03 ` Marc Zyngier
2025-02-27 0:33 ` [PATCH 3/6] KVM: arm64: Introduce {get,set}_host_state() helpers Quentin Perret
2025-02-27 0:33 ` [PATCH 4/6] KVM: arm64: Move hyp state to hyp_vmemmap Quentin Perret
2025-03-03 9:47 ` Vincent Donnefort
2025-03-13 19:13 ` Quentin Perret
2025-03-14 11:31 ` Marc Zyngier
2025-03-14 14:06 ` Quentin Perret
2025-03-16 11:08 ` Marc Zyngier
2025-02-27 0:33 ` [PATCH 5/6] KVM: arm64: Defer EL2 stage-1 mapping on share Quentin Perret
2025-02-27 0:33 ` [PATCH 6/6] KVM: arm64: Unconditionally cross check hyp state Quentin Perret
2025-03-16 11:12 ` [PATCH 0/6] Move pKVM ownership state to hyp_vmemmap 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=20250227003310.367350-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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox