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: Fuad Tabba <tabba@google.com>,
Vincent Donnefort <vdonnefort@google.com>,
Sebastian Ene <sebastianene@google.com>,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 00/18] KVM: arm64: Non-protected guest stage-2 support for pKVM
Date: Tue, 3 Dec 2024 10:37:17 +0000 [thread overview]
Message-ID: <20241203103735.2267589-1-qperret@google.com> (raw)
Hi all,
This is the v2 of the series adding support for non-protected guests to
pKVM. Please refer to v1 for all the context:
https://lore.kernel.org/kvmarm/20241104133204.85208-1-qperret@google.com/
The series is organized as follows:
- Patches 01 to 04 move the host ownership state tracking from the
host's stage-2 page-table to the hypervisor's vmemmap. This avoids
fragmenting the host stage-2 for shared pages, which is only needed
to store an annotation in the SW bits of the corresponding PTE. All
pages mapped into non-protected guests are shared from pKVM's PoV,
so the cost of stage-2 fragmentation will increase massively as we
start tracking that at EL2. Note that these patches also help with
the existing sharing for e.g. FF-A, so they could possibly be merged
separately from the rest of the series.
- Patches 05 to 07 implement a minor refactoring of the pgtable code to
ease the integration of the pKVM MMU later on.
- Patches 08 to 16 introduce all the infrastructure needed on the pKVM
side for handling guest stage-2 page-tables at EL2.
- Patches 17 and 18 plumb the newly introduced pKVM support into
KVM/arm64.
Patches based on 6.13-rc1, tested on Pixel 6 and Qemu.
Changes in v2:
- Rebased on 6.13-rc1 (small conflicts with 2362506f7cff ("KVM: arm64:
Don't mark "struct page" accessed when making SPTE young") in
particular)
- Fixed kerneldoc breakage for __unmap_stage2_range()
- Fixed pkvm_pgtable_test_clear_young() to use correct HVC
- Folded guest_get_valid_pte() into __check_host_unshare_guest() for
clarity
Thanks,
Quentin
Marc Zyngier (1):
KVM: arm64: Introduce __pkvm_vcpu_{load,put}()
Quentin Perret (17):
KVM: arm64: Change the layout of enum pkvm_page_state
KVM: arm64: Move enum pkvm_page_state to memory.h
KVM: arm64: Make hyp_page::order a u8
KVM: arm64: Move host page ownership tracking to the hyp vmemmap
KVM: arm64: Pass walk flags to kvm_pgtable_stage2_mkyoung
KVM: arm64: Pass walk flags to kvm_pgtable_stage2_relax_perms
KVM: arm64: Make kvm_pgtable_stage2_init() a static inline function
KVM: arm64: Add {get,put}_pkvm_hyp_vm() helpers
KVM: arm64: Introduce __pkvm_host_share_guest()
KVM: arm64: Introduce __pkvm_host_unshare_guest()
KVM: arm64: Introduce __pkvm_host_relax_guest_perms()
KVM: arm64: Introduce __pkvm_host_wrprotect_guest()
KVM: arm64: Introduce __pkvm_host_test_clear_young_guest()
KVM: arm64: Introduce __pkvm_host_mkyoung_guest()
KVM: arm64: Introduce __pkvm_tlb_flush_vmid()
KVM: arm64: Introduce the EL1 pKVM MMU
KVM: arm64: Plumb the pKVM MMU in KVM
arch/arm64/include/asm/kvm_asm.h | 9 +
arch/arm64/include/asm/kvm_host.h | 4 +
arch/arm64/include/asm/kvm_pgtable.h | 42 ++-
arch/arm64/include/asm/kvm_pkvm.h | 28 ++
arch/arm64/kvm/arm.c | 23 +-
arch/arm64/kvm/hyp/include/nvhe/gfp.h | 6 +-
arch/arm64/kvm/hyp/include/nvhe/mem_protect.h | 38 +--
arch/arm64/kvm/hyp/include/nvhe/memory.h | 43 ++-
arch/arm64/kvm/hyp/include/nvhe/pkvm.h | 15 +
arch/arm64/kvm/hyp/nvhe/hyp-main.c | 210 +++++++++++-
arch/arm64/kvm/hyp/nvhe/mem_protect.c | 312 ++++++++++++++++--
arch/arm64/kvm/hyp/nvhe/page_alloc.c | 14 +-
arch/arm64/kvm/hyp/nvhe/pkvm.c | 56 ++++
arch/arm64/kvm/hyp/nvhe/setup.c | 7 +-
arch/arm64/kvm/hyp/pgtable.c | 13 +-
arch/arm64/kvm/mmu.c | 109 ++++--
arch/arm64/kvm/pkvm.c | 195 +++++++++++
arch/arm64/kvm/vgic/vgic-v3.c | 6 +-
18 files changed, 987 insertions(+), 143 deletions(-)
--
2.47.0.338.g60cca15819-goog
next reply other threads:[~2024-12-03 10:37 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 10:37 Quentin Perret [this message]
2024-12-03 10:37 ` [PATCH v2 01/18] KVM: arm64: Change the layout of enum pkvm_page_state Quentin Perret
2024-12-10 12:59 ` Fuad Tabba
2024-12-10 15:15 ` Quentin Perret
2024-12-03 10:37 ` [PATCH v2 02/18] KVM: arm64: Move enum pkvm_page_state to memory.h Quentin Perret
2024-12-03 10:37 ` [PATCH v2 03/18] KVM: arm64: Make hyp_page::order a u8 Quentin Perret
2024-12-03 10:37 ` [PATCH v2 04/18] KVM: arm64: Move host page ownership tracking to the hyp vmemmap Quentin Perret
2024-12-10 13:02 ` Fuad Tabba
2024-12-10 15:29 ` Quentin Perret
2024-12-10 15:46 ` Fuad Tabba
2024-12-03 10:37 ` [PATCH v2 05/18] KVM: arm64: Pass walk flags to kvm_pgtable_stage2_mkyoung Quentin Perret
2024-12-03 10:37 ` [PATCH v2 06/18] KVM: arm64: Pass walk flags to kvm_pgtable_stage2_relax_perms Quentin Perret
2024-12-03 10:37 ` [PATCH v2 07/18] KVM: arm64: Make kvm_pgtable_stage2_init() a static inline function Quentin Perret
2024-12-03 10:37 ` [PATCH v2 08/18] KVM: arm64: Add {get,put}_pkvm_hyp_vm() helpers Quentin Perret
2024-12-03 10:37 ` [PATCH v2 09/18] KVM: arm64: Introduce __pkvm_vcpu_{load,put}() Quentin Perret
2024-12-03 10:37 ` [PATCH v2 10/18] KVM: arm64: Introduce __pkvm_host_share_guest() Quentin Perret
2024-12-10 13:58 ` Fuad Tabba
2024-12-10 15:41 ` Quentin Perret
2024-12-10 15:51 ` Fuad Tabba
2024-12-11 9:58 ` Quentin Perret
2024-12-11 10:07 ` Fuad Tabba
2024-12-11 10:14 ` Quentin Perret
2024-12-11 10:21 ` Quentin Perret
2024-12-11 10:32 ` Fuad Tabba
2024-12-03 10:37 ` [PATCH v2 11/18] KVM: arm64: Introduce __pkvm_host_unshare_guest() Quentin Perret
2024-12-10 14:41 ` Fuad Tabba
2024-12-10 15:53 ` Quentin Perret
2024-12-10 15:57 ` Fuad Tabba
2024-12-03 10:37 ` [PATCH v2 12/18] KVM: arm64: Introduce __pkvm_host_relax_guest_perms() Quentin Perret
2024-12-10 14:56 ` Fuad Tabba
2024-12-11 8:57 ` Quentin Perret
2024-12-03 10:37 ` [PATCH v2 13/18] KVM: arm64: Introduce __pkvm_host_wrprotect_guest() Quentin Perret
2024-12-10 15:06 ` Fuad Tabba
2024-12-10 19:38 ` Quentin Perret
2024-12-03 10:37 ` [PATCH v2 14/18] KVM: arm64: Introduce __pkvm_host_test_clear_young_guest() Quentin Perret
2024-12-10 15:11 ` Fuad Tabba
2024-12-10 19:39 ` Quentin Perret
2024-12-03 10:37 ` [PATCH v2 15/18] KVM: arm64: Introduce __pkvm_host_mkyoung_guest() Quentin Perret
2024-12-10 15:14 ` Fuad Tabba
2024-12-10 19:46 ` Quentin Perret
2024-12-11 10:11 ` Fuad Tabba
2024-12-11 10:18 ` Quentin Perret
2024-12-03 10:37 ` [PATCH v2 16/18] KVM: arm64: Introduce __pkvm_tlb_flush_vmid() Quentin Perret
2024-12-10 15:23 ` Fuad Tabba
2024-12-11 10:03 ` Quentin Perret
2024-12-11 10:21 ` Fuad Tabba
2024-12-03 10:37 ` [PATCH v2 17/18] KVM: arm64: Introduce the EL1 pKVM MMU Quentin Perret
2024-12-12 11:35 ` Marc Zyngier
2024-12-12 12:03 ` Quentin Perret
2024-12-03 10:37 ` [PATCH v2 18/18] KVM: arm64: Plumb the pKVM MMU in KVM Quentin Perret
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=20241203103735.2267589-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=sebastianene@google.com \
--cc=suzuki.poulose@arm.com \
--cc=tabba@google.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
all inboxes | Powered by JetHome®