mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: Marc Zyngier <maz@kernel.org>, Fuad Tabba <tabba@google.com>
Cc: 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
Date: Sat, 3 Oct 2026 08:07:39 +0100	[thread overview]
Message-ID: <d7a398b3-5cbe-4a1c-bdd3-c1c5925dfc33@arm.com> (raw)
In-Reply-To: <83e79119-b331-4640-b2c7-cc8135d71c77@arm.com>

On 03/10/2026 06:53, Suzuki K Poulose wrote:
> On 02/10/2026 16:29, Marc Zyngier wrote:
>> On Fri, 02 Oct 2026 15:37:00 +0100,
>> Fuad Tabba <tabba@google.com> wrote:
>>>
>>> Hi Marc,
>>>
>>> On Fri, 02 Oct 2026 15:15:06 +0100, Marc Zyngier <maz@kernel.org> wrote:
>>> [...]
>>>> Honestly, we introduce the flavor stuff to make it easy to match
>>>> things on a particular VM type in a readable way. So why isn't this
>>>> reading:
>>>>
>>>>          if (vcpu->kvm->arch.vm_flavor != VM_PROTECTED_PKVM)
>>>>                  return;
>>>
>>> I know this is a sketch, but just in case: that's inverted. The sync
>>> only applies to non-protected pKVM VMs (EL2 ignores it for protected
>>> ones), so it would be != VM_PKVM.
>>
>> See what I meant about this stuff being completely intractable? I
>> still have no idea what it means! ;-)
>>
> 
> Just to be clear: unprotected_pkvm() != (vm_flavor != VM_PROTECED_PKVM).
> Rather, unprotected_pkvm => (vm_flavor == VM_PKVM).
> 
> And the code wanted to bail out early for !unprotected_pkvm(). We can
> stick in "is_protected_kvm_enabled()" for unprotected_pkvm predicate
> 
> But, I can drop the helper and use the vm_flavor check.

FWIW: Here is the diff for the above change. If you are happy
with the following, I could fold this in.


diff --git a/arch/arm64/kvm/arm.c b/arch/arm64/kvm/arm.c
index 90547fbbc8ad7..bcec14c587119 100644
--- a/arch/arm64/kvm/arm.c
+++ b/arch/arm64/kvm/arm.c
@@ -772,7 +772,7 @@ void kvm_arch_vcpu_put(struct kvm_vcpu *vcpu)
                 kvm_call_hyp_nvhe(__pkvm_vcpu_put);

                 /* __pkvm_vcpu_put implies a sync of the state */
-               if (kvm_vm_is_unprotected_pkvm(vcpu->kvm))
+               if (vcpu->kvm->arch.vm_flavor == VM_PKVM)
                         vcpu_set_flag(vcpu, PKVM_HOST_STATE_DIRTY);
         }

@@ -1006,7 +1006,7 @@ int kvm_arch_vcpu_run_pid_change(struct kvm_vcpu 
*vcpu)

         if (is_protected_kvm_enabled()) {
                 /* Start with the vcpu in a dirty state */
-               if (kvm_vm_is_unprotected_pkvm(vcpu->kvm))
+               if (vcpu->kvm->arch.vm_flavor == VM_PKVM)
                         vcpu_set_flag(vcpu, PKVM_HOST_STATE_DIRTY);
                 ret = pkvm_create_hyp_vm(kvm);
                 if (ret)
diff --git a/arch/arm64/kvm/handle_exit.c b/arch/arm64/kvm/handle_exit.c
index 384c5d258c7f8..4e16e7d165515 100644
--- a/arch/arm64/kvm/handle_exit.c
+++ b/arch/arm64/kvm/handle_exit.c
@@ -490,7 +490,7 @@ static void handle_exit_pkvm_state(struct kvm_vcpu 
*vcpu, int exception_index)
  {
         int exception_code = ARM_EXCEPTION_CODE(exception_index);

-       if (!kvm_vm_is_unprotected_pkvm(vcpu->kvm))
+       if (!is_protected_kvm_enabled() || vcpu->kvm->arch.vm_flavor != 
VM_PKVM)
                 return;

         /*



Cheers
Suzuki>
> Cheers
> Suzuki
> 
>>     M.
>>
> 


  reply	other threads:[~2026-10-03  7:07 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-01 21:06 [PATCH v21 00/23] KVM: arm64: CCA: Add basic plumbing for Realms Suzuki K Poulose
2026-10-01 21:06 ` [PATCH v21 01/23] KVM: arm64: protected VM: Handle user writes to CNTVCT_EL0/CNTPCT_EL0 Suzuki K Poulose
2026-10-01 21:06 ` [PATCH v21 02/23] KVM: arm64: Disable Steal time accounting for protected guests Suzuki K Poulose
2026-10-01 21:06 ` [PATCH v21 03/23] KVM: arm64: Include kvm_emulate.h in kvm/arm_psci.h Suzuki K Poulose
2026-10-01 21:06 ` [PATCH v21 04/23] KVM: arm64: Avoid including linux/kvm_host.h in kvm_pgtable.h Suzuki K Poulose
2026-10-01 21:06 ` [PATCH v21 05/23] KVM: arm64: Track the type of VM in kvm_arch Suzuki K Poulose
2026-10-02 10:06   ` Fuad Tabba
2026-10-02 12:57     ` Marc Zyngier
2026-10-02 13:05       ` Fuad Tabba
2026-10-02 13:10         ` Suzuki K Poulose
2026-10-02 13:34         ` Marc Zyngier
2026-10-02 14:15         ` Marc Zyngier
2026-10-02 14:37           ` Fuad Tabba
2026-10-02 15:29             ` Marc Zyngier
2026-10-02 15:30               ` Fuad Tabba
2026-10-03  5:53               ` Suzuki K Poulose
2026-10-03  7:07                 ` Suzuki K Poulose [this message]
2026-10-03  8:45                   ` Marc Zyngier
2026-10-02 15:15           ` Suzuki K Poulose
2026-10-02 15:40             ` Marc Zyngier
2026-10-02 15:42               ` Suzuki K Poulose
2026-10-01 21:06 ` [PATCH v21 06/23] KVM: arm64: Don't call vcpu_set_pauth_traps for pKVM host Suzuki K Poulose
2026-10-01 21:06 ` [PATCH v21 07/23] KVM: arm64: Refactor the vcpu_load to allow for VM specific callbacks Suzuki K Poulose
2026-10-01 21:06 ` [PATCH v21 08/23] KVM: arm64: Add vcpu load/put call backs for flavors Suzuki K Poulose
2026-10-01 21:06 ` [PATCH v21 09/23] KVM: arm64: Reuse kvm_stage2_unmap_range in kvm_unmap_gfn_range Suzuki K Poulose
2026-10-01 21:06 ` [PATCH v21 10/23] KVM: arm64: Add VM specific callback for S2 MMU operations Suzuki K Poulose
2026-10-02 10:19   ` Fuad Tabba
2026-10-02 10:29     ` Suzuki K Poulose
2026-10-03  9:01   ` Marc Zyngier
2026-10-01 21:06 ` [PATCH v21 11/23] KVM: arm64: Use a local kvm pointer in kvm_handle_guest_abort() Suzuki K Poulose
2026-10-02  9:14   ` Fuad Tabba
2026-10-01 21:06 ` [PATCH v21 12/23] KVM: arm64: Abstract out memory abort handling Suzuki K Poulose
2026-10-01 21:06 ` [PATCH v21 13/23] KVM: arm64: Mandate VGIC v3 for pKVM VMs and Realms Suzuki K Poulose
2026-10-02  9:23   ` Fuad Tabba
2026-10-01 21:06 ` [PATCH v21 14/23] KVM: arm64: CCA: Add a new mode for supporting Realm guests Suzuki K Poulose
2026-10-01 21:06 ` [PATCH v21 15/23] KVM: arm64: CCA: Add VCPU load/put for Realms Suzuki K Poulose
2026-10-01 21:06 ` [PATCH v21 16/23] KVM: arm64: CCA: Add bare minimal S2 operations for Realm Suzuki K Poulose
2026-10-01 21:06 ` [PATCH v21 17/23] KVM: arm64: CCA: Introduce Realms Suzuki K Poulose
2026-10-01 21:06 ` [PATCH v21 18/23] KVM: arm64: CCA: Don't expose unsupported capabilities for realm guests Suzuki K Poulose
2026-10-02  9:34   ` Fuad Tabba
2026-10-02  9:36     ` Suzuki K Poulose
2026-10-01 21:06 ` [PATCH v21 19/23] KVM: arm64: Prevent unsupported vcpu features for VM types Suzuki K Poulose
2026-10-01 21:07 ` [PATCH v21 20/23] KVM: arm64: CCA: WARN on injected undef exceptions Suzuki K Poulose
2026-10-01 21:07 ` [PATCH v21 21/23] KVM: arm64: CCA: Support timers in realm RECs Suzuki K Poulose
2026-10-01 21:07 ` [PATCH v21 22/23] KVM: arm64: CCA: Expose SVE VL register before VCPU finalization Suzuki K Poulose
2026-10-01 21:07 ` [PATCH v21 23/23] KVM: arm64: CCA: Control user register access for Realms Suzuki K Poulose
2026-10-01 21:41 ` [PATCH v21 00/23] KVM: arm64: CCA: Add basic plumbing " Gavin Shan
2026-10-02  6:13   ` 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=d7a398b3-5cbe-4a1c-bdd3-c1c5925dfc33@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=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

all inboxes | Powered by JetHome®