From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 016BDCA5FDD for ; Fri, 2 Oct 2026 15:40:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:Content-Type:MIME-Version: References:In-Reply-To:Subject:Cc:To:From:Message-ID:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=KQtBKmV1C9YgjiIXLvcIFbStd7xUmxqWxSJXNgv5TuM=; b=L7vWlCSZpE2jw4G57kM7sn43VQ 8Hmxo20AIBLVjeHLa3Y4B5J0BIzIJcWMJy2hA0uorufyzwyU+8ZdXTPjptRLtfz29lJZnshtM5mzt AFORTTGGkmK3s0TN5P0ivyzdIzSFYkKadVtXSsCxkVruhparMDBFFeGb5aFONwmZxN+JPId3VhF4V EzYRVaAGwE/JWlWtUdFWbcK4zXyVSEzJYqKya2n8q4MTzqHlbjHBdt1doQBZIXQTva0EM+PiYp1va LCYyNpqvabc0LKos2UmHDyM5xjLa7rHweILU/tE7RmLhnOSvA5M/HG7QDMd4CsEOzNxHkOQNylIM5 V17Il9wA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.99.1 #2 (Red Hat Linux)) id 1xCfNC-0000000BxfR-2lOW; Fri, 02 Oct 2026 15:40:34 +0000 Received: from tor.source.kernel.org ([2600:3c04:e001:324:0:1991:8:25]) by bombadil.infradead.org with esmtps (Exim 4.99.1 #2 (Red Hat Linux)) id 1xCfNB-0000000BxeP-0H8n for linux-arm-kernel@lists.infradead.org; Fri, 02 Oct 2026 15:40:33 +0000 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) by tor.source.kernel.org (Postfix) with ESMTP id A67C360A93; Fri, 2 Oct 2026 15:40:31 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 58AD21F000FF; Fri, 2 Oct 2026 15:40:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1790955631; bh=KQtBKmV1C9YgjiIXLvcIFbStd7xUmxqWxSJXNgv5TuM=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=anbTS0laiuDH50SzRWiL6aysLxMhhzzXx/rR8C8pOoYslb9VfJGkETKebTRUJRMey ls7sW1OaQEblook8tu19AVAOWbehkhDX3/vi5Ppy2vXwXvCAzJsrFGZ0L0GIk9u31a RQ42/R7+klv4pJp85W4ahFy5bAzYI7+K1Xm7m8utqNXxrHqJD+oiGqytW2/G6pvflT FhnI5a9C3sbjM5NFrdA++WnhvpyiXbDVgIF/TqDpKBxiffTh2vi80jMu4N0XrOwYz7 Rlo//OVH1qnjQupD7gTnP+5b4msupwwgKrw5xIAW03va3yEbErSFWV9FM4Oy4CWMCp 8us7eAXO/UkUA== Received: from sofa.misterjones.org ([185.219.108.64] helo=goblin-girl.misterjones.org) by disco-boy.misterjones.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xCfN7-0000000GI1q-0qgJ; Fri, 02 Oct 2026 15:40:29 +0000 Date: Fri, 02 Oct 2026 16:40:28 +0100 Message-ID: <86mrsw2jrn.wl-maz@kernel.org> From: Marc Zyngier To: Suzuki K Poulose Cc: Fuad Tabba , kvm@vger.kernel.org, kvmarm@lists.linux.dev, 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, 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 Subject: Re: [PATCH v21 05/23] KVM: arm64: Track the type of VM in kvm_arch In-Reply-To: <10563362-5964-4ef7-b5d7-fe1d67ce4adb@arm.com> References: <20261001210703.1597150-1-suzuki.poulose@arm.com> <20261001210703.1597150-6-suzuki.poulose@arm.com> <86se2o2rbs.wl-maz@kernel.org> <86pkxs2npx.wl-maz@kernel.org> <10563362-5964-4ef7-b5d7-fe1d67ce4adb@arm.com> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM-LB/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL-LB/10.8 EasyPG/1.0.0 Emacs/30.1 (aarch64-unknown-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII X-SA-Exim-Connect-IP: 185.219.108.64 X-SA-Exim-Rcpt-To: suzuki.poulose@arm.com, tabba@google.com, kvm@vger.kernel.org, kvmarm@lists.linux.dev, 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, 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 X-SA-Exim-Mail-From: maz@kernel.org X-SA-Exim-Scanned: No (on disco-boy.misterjones.org); SAEximRunCond expanded to false X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Fri, 02 Oct 2026 16:15:07 +0100, Suzuki K Poulose wrote: > > > diff --git a/arch/arm64/kvm/mmu.c b/arch/arm64/kvm/mmu.c > > index 0f4e8b71fa85d..9ba86450fe4af 100644 > > --- a/arch/arm64/kvm/mmu.c > > +++ b/arch/arm64/kvm/mmu.c > > @@ -2624,7 +2624,7 @@ int kvm_arch_prepare_memory_region(struct kvm *kvm, > > hva_t hva, reg_end; > > int ret = 0; > > - if (kvm_vm_is_protected_pkvm(kvm)) { > > + if (kvm_vm_is_protected(kvm)) { > > We have slightly different handling for Realms. The final code for this > looks like : > > if (kvm_vm_is_protected(kvm)) { > if (new && > new->flags & (KVM_MEM_LOG_DIRTY_PAGES | KVM_MEM_READONLY)) { > return -EPERM; > } > } > > if (kvm_vm_is_protected_pkvm(kvm)) { > /* Cannot modify memslots once a pVM has run. */ > if (pkvm_hyp_vm_is_created(kvm) && > (change == KVM_MR_DELETE || change == KVM_MR_MOVE)) { > return -EPERM; > } > } else if (kvm_realm_is_created(kvm)) { > /* > * Once the Realm is created, we cannot modify any slots that > * could be providing private memory. i.e., guest_memfd backed > * slots. > * TODO: Handle trusted device private memory slots > */ > if (kvm_slot_has_gmem(old) || kvm_slot_has_gmem(new)) > return -EPERM; > } > > > Of course we could invert the checks to detect vm_is_protected_pkvm() This is how I expect this stuff to be written. if (kvm_vm_is_protected(kvm) && new && new->flags & (KVM_MEM_LOG_DIRTY_PAGES | KVM_MEM_READONLY)) return -EPERM; switch (kvm->vm_flavor) { case VM_PROTECTED_PKVM: /* Cannot modify memslots once a pVM has run. */ if (pkvm_hyp_vm_is_created(kvm) && (change == KVM_MR_DELETE || change == KVM_MR_MOVE)) { return -EPERM; break; case VM_CCA: /* * Once the Realm is created, we cannot modify any slots that * could be providing private memory. i.e., guest_memfd backed * slots. * TODO: Handle trusted device private memory slots */ if (kvm_realm_is_created(kvm) && (kvm_slot_has_gmem(old) || kvm_slot_has_gmem(new))) return -EPERM; break; default: break; } We have an enumeration. Make use of it. And the whole "is_created" crap needs to be sorted one way or another. M. -- Without deviation from the norm, progress is not possible.