From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: kvm@vger.kernel.org, kvmarm@lists.linux.dev
Cc: maz@kernel.org, will@kernel.org, catalin.marinas@arm.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, steven.price@arm.com,
aneesh.kumar@kernel.org, oupton@kernel.org, gshan@redhat.com,
joey.gouly@arm.com, tabba@google.com, yuzenghui@huawei.com,
linux-coco@lists.linux.dev, gankulkarni@os.amperecomputing.com,
sdonthineni@nvidia.com, alpergun@google.com,
fj0570is@fujitsu.com, WeiLin.Chang@arm.com,
lpieralisi@kernel.org, enju.kohei@fujitsu.com,
sudeep.holla@arm.com, jonathan.cameron@oss.qualcomm.com,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Fuad Tabba <fuad.tabba@linux.dev>
Subject: [PATCH v20 09/22] KVM: arm64: Reuse kvm_stage2_unmap_range in kvm_unmap_gfn_range
Date: Thu, 24 Sep 2026 17:04:51 +0100 [thread overview]
Message-ID: <20260924160504.853911-10-suzuki.poulose@arm.com> (raw)
In-Reply-To: <20260924160504.853911-1-suzuki.poulose@arm.com>
In preparation for adding VM specific backends for stage2 operation,
switch to kvm_stage2_unmap_range() instead of __unmap_stage2_range()
from the kvm_unmap_gfn_range(). Drop the bail out check for protected
VMs and defer that to the one in kvm_stage2_unmap_range(). Later we
would replace the logic in kvm_stage2_unmap_range() with VM specific
backends.
No functional changes intended.
Reviewed-by: Fuad Tabba <fuad.tabba@linux.dev>
Reviewed-by: Jonathan Cameron <jonathan.cameron@oss.qualcomm.com>
Tested-by: Gavin Shan <gshan@redhat.com>
Signed-off-by: Suzuki K Poulose <suzuki.poulose@arm.com>
---
arch/arm64/kvm/mmu.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/arm64/kvm/mmu.c b/arch/arm64/kvm/mmu.c
index 0f4e8b71fa85d..365e2a12c2348 100644
--- a/arch/arm64/kvm/mmu.c
+++ b/arch/arm64/kvm/mmu.c
@@ -2436,12 +2436,12 @@ int kvm_handle_guest_abort(struct kvm_vcpu *vcpu)
bool kvm_unmap_gfn_range(struct kvm *kvm, struct kvm_gfn_range *range)
{
- if (!kvm->arch.mmu.pgt || kvm_vm_is_protected(kvm))
+ if (!kvm->arch.mmu.pgt)
return false;
- __unmap_stage2_range(&kvm->arch.mmu, range->start << PAGE_SHIFT,
- (range->end - range->start) << PAGE_SHIFT,
- range->may_block);
+ kvm_stage2_unmap_range(&kvm->arch.mmu, range->start << PAGE_SHIFT,
+ (range->end - range->start) << PAGE_SHIFT,
+ range->may_block);
kvm_nested_s2_unmap(kvm, range->may_block);
return false;
--
2.43.0
next prev parent reply other threads:[~2026-09-24 16:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 16:04 [PATCH v20 00/22] KVM: arm64: CCA: Add basic plumbing for Realms Suzuki K Poulose
2026-09-24 16:04 ` [PATCH v20 01/22] KVM: arm64: protected VM: Handle user writes to CNTVCT_EL0/CNTPCT_EL0 Suzuki K Poulose
2026-09-24 16:04 ` [PATCH v20 02/22] KVM: arm64: Disable Steal time accounting for protected guests Suzuki K Poulose
2026-09-24 16:04 ` [PATCH v20 03/22] KVM: arm64: Include kvm_emulate.h in kvm/arm_psci.h Suzuki K Poulose
2026-09-24 16:04 ` [PATCH v20 04/22] KVM: arm64: Avoid including linux/kvm_host.h in kvm_pgtable.h Suzuki K Poulose
2026-09-24 16:04 ` [PATCH v20 05/22] KVM: arm64: Track the type of VM in kvm_arch Suzuki K Poulose
2026-09-24 16:04 ` [PATCH v20 06/22] KVM: arm64: Don't call vcpu_set_pauth_traps for pKVM host Suzuki K Poulose
2026-09-24 16:04 ` [PATCH v20 07/22] KVM: arm64: Refactor the vcpu_load to allow for VM specific callbacks Suzuki K Poulose
2026-09-24 16:04 ` [PATCH v20 08/22] KVM: arm64: Add vcpu load/put call backs for flavors Suzuki K Poulose
2026-09-24 16:04 ` Suzuki K Poulose [this message]
2026-09-24 16:04 ` [PATCH v20 10/22] KVM: arm64: Add VM specific callback for S2 MMU operations Suzuki K Poulose
2026-09-24 16:04 ` [PATCH v20 11/22] KVM: arm64: Use a local kvm pointer in kvm_handle_guest_abort() Suzuki K Poulose
2026-09-24 16:04 ` [PATCH v20 12/22] KVM: arm64: Abstract out memory abort handling Suzuki K Poulose
2026-09-24 16:04 ` [PATCH v20 13/22] KVM: arm64: Mandate VGIC v3 for pKVM VMs and Realms Suzuki K Poulose
2026-09-24 16:04 ` [PATCH v20 14/22] KVM: arm64: CCA: Add a new mode for supporting Realm guests Suzuki K Poulose
2026-09-24 16:04 ` [PATCH v20 15/22] KVM: arm64: CCA: Add VCPU load/put for Realms Suzuki K Poulose
2026-09-24 16:04 ` [PATCH v20 16/22] KVM: arm64: CCA: Add bare minimal S2 operations for Realm Suzuki K Poulose
2026-09-24 16:04 ` [PATCH v20 17/22] KVM: arm64: CCA: Introduce Realms Suzuki K Poulose
2026-09-24 16:05 ` [PATCH v20 18/22] KVM: arm64: CCA: Don't expose unsupported capabilities for realm guests Suzuki K Poulose
2026-09-24 16:05 ` [PATCH v20 19/22] KVM: arm64: CCA: WARN on injected undef exceptions Suzuki K Poulose
2026-09-24 16:05 ` [PATCH v20 20/22] KVM: arm64: CCA: Support timers in realm RECs Suzuki K Poulose
2026-09-24 16:05 ` [PATCH v20 21/22] KVM: arm64: CCA: Expose SVE VL register before VCPU finalization Suzuki K Poulose
2026-09-24 16:05 ` [PATCH v20 22/22] KVM: arm64: CCA: Control user register access for Realms Suzuki K Poulose
2026-10-01 15:53 ` Catalin Marinas
2026-10-01 16:37 ` Suzuki K Poulose
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=20260924160504.853911-10-suzuki.poulose@arm.com \
--to=suzuki.poulose@arm.com \
--cc=WeiLin.Chang@arm.com \
--cc=alpergun@google.com \
--cc=aneesh.kumar@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=enju.kohei@fujitsu.com \
--cc=fj0570is@fujitsu.com \
--cc=fuad.tabba@linux.dev \
--cc=gankulkarni@os.amperecomputing.com \
--cc=gshan@redhat.com \
--cc=joey.gouly@arm.com \
--cc=jonathan.cameron@oss.qualcomm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=maz@kernel.org \
--cc=oupton@kernel.org \
--cc=sdonthineni@nvidia.com \
--cc=steven.price@arm.com \
--cc=sudeep.holla@arm.com \
--cc=tabba@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