From: Yan Zhao <yan.y.zhao@intel.com>
To: Sean Christopherson <seanjc@google.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
"Jethro Beekman" <jethro@fortanix.com>,
"Alexander Potapenko" <glider@google.com>,
"Carlos López" <clopez@suse.de>
Subject: Re: [PATCH 12/21] KVM: SEV: WARN on unhandled VM type when initializing VM
Date: Thu, 9 Apr 2026 13:12:02 +0800 [thread overview]
Message-ID: <adc1IrD8uqWdaOKv@yzhao56-desk.sh.intel.com> (raw)
In-Reply-To: <20260310234829.2608037-13-seanjc@google.com>
On Tue, Mar 10, 2026 at 04:48:20PM -0700, Sean Christopherson wrote:
> WARN if KVM encounters an unhandled VM type when setting up flags for SEV+
> VMs, e.g. to guard against adding a new flavor of SEV without adding proper
> recognition in sev_vm_init().
>
> Practically speaking, no functional change intended (the new "default" case
> should be unreachable).
>
> Signed-off-by: Sean Christopherson <seanjc@google.com>
> ---
> arch/x86/kvm/svm/sev.c | 29 ++++++++++++++++++-----------
> 1 file changed, 18 insertions(+), 11 deletions(-)
>
> diff --git a/arch/x86/kvm/svm/sev.c b/arch/x86/kvm/svm/sev.c
> index e5dae76d2986..9a907bc057d0 100644
> --- a/arch/x86/kvm/svm/sev.c
> +++ b/arch/x86/kvm/svm/sev.c
> @@ -2930,17 +2930,24 @@ static int snp_decommission_context(struct kvm *kvm)
>
> void sev_vm_init(struct kvm *kvm)
> {
> - int type = kvm->arch.vm_type;
> -
> - if (type == KVM_X86_DEFAULT_VM || type == KVM_X86_SW_PROTECTED_VM)
> - return;
> -
> - kvm->arch.has_protected_state = (type == KVM_X86_SEV_ES_VM ||
> - type == KVM_X86_SNP_VM);
> - to_kvm_sev_info(kvm)->need_init = true;
> -
> - kvm->arch.has_private_mem = (type == KVM_X86_SNP_VM);
> - kvm->arch.pre_fault_allowed = !kvm->arch.has_private_mem;
> + switch (kvm->arch.vm_type) {
> + case KVM_X86_DEFAULT_VM:
> + case KVM_X86_SW_PROTECTED_VM:
> + break;
> + case KVM_X86_SNP_VM:
> + kvm->arch.has_private_mem = true;
> + fallthrough;
> + case KVM_X86_SEV_ES_VM:
> + kvm->arch.has_protected_state = true;
> + fallthrough;
> + case KVM_X86_SEV_VM:
> + kvm->arch.pre_fault_allowed = !kvm->arch.has_private_mem;
> + to_kvm_sev_info(kvm)->need_init = true;
> + break;
> + default:
> + WARN_ONCE(1, "Unsupported VM type %lu", kvm->arch.vm_type);
After pulling the latest kvm-x86/next, I encountered this compilation warning:
"arch/x86/kvm/svm/sev.c:2954:30: error: format %lu expects argument of type long
unsigned int, but argument 2 has type int [-Werror=format=]",
So,
diff --git a/arch/x86/kvm/svm/sev.c b/arch/x86/kvm/svm/sev.c
index 75d0c03d69bc..ca09c06d1e80 100644
--- a/arch/x86/kvm/svm/sev.c
+++ b/arch/x86/kvm/svm/sev.c
@@ -2951,7 +2951,7 @@ void sev_vm_init(struct kvm *kvm)
to_kvm_sev_info(kvm)->need_init = true;
break;
default:
- WARN_ONCE(1, "Unsupported VM type %lu", kvm->arch.vm_type);
+ WARN_ONCE(1, "Unsupported VM type %u", kvm->arch.vm_type);
break;
}
}
> + break;
> + }
> }
>
> void sev_vm_destroy(struct kvm *kvm)
> --
> 2.53.0.473.g4a7958ca14-goog
>
>
next prev parent reply other threads:[~2026-04-09 5:51 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 23:48 [PATCH 00/21] Fixes and lock cleanup+hardening Sean Christopherson
2026-03-10 23:48 ` [PATCH 01/21] KVM: selftests: Remove duplicate LAUNCH_UPDATE_VMSA call in SEV-ES migrate test Sean Christopherson
2026-03-10 23:48 ` [PATCH 02/21] KVM: SEV: Reject attempts to sync VMSA of an already-launched/encrypted vCPU Sean Christopherson
2026-03-10 23:48 ` [PATCH 03/21] KVM: SEV: Protect *all* of sev_mem_enc_register_region() with kvm->lock Sean Christopherson
2026-03-10 23:48 ` [PATCH 04/21] KVM: SEV: Disallow LAUNCH_FINISH if vCPUs are actively being created Sean Christopherson
2026-03-10 23:48 ` [PATCH 05/21] KVM: SEV: Lock all vCPUs when synchronzing VMSAs for SNP launch finish Sean Christopherson
2026-04-08 14:07 ` Aithal, Srikanth
2026-04-08 18:42 ` Sean Christopherson
2026-04-09 5:12 ` Aithal, Srikanth
2026-03-10 23:48 ` [PATCH 06/21] KVM: SEV: Lock all vCPUs for the duration of SEV-ES VMSA synchronization Sean Christopherson
2026-03-10 23:48 ` [PATCH 07/21] KVM: SEV: Provide vCPU-scoped accessors for detecting SEV+ guests Sean Christopherson
2026-03-10 23:48 ` [PATCH 08/21] KVM: SEV: Add quad-underscore version of VM-scoped APIs to detect " Sean Christopherson
2026-03-10 23:48 ` [PATCH 09/21] KVM: SEV: Document the SEV-ES check when querying SMM support as "safe" Sean Christopherson
2026-03-10 23:48 ` [PATCH 10/21] KVM: SEV: Move standard VM-scoped helpers to detect SEV+ guests to sev.c Sean Christopherson
2026-03-17 10:33 ` Alexander Potapenko
2026-03-31 18:42 ` Sean Christopherson
2026-03-10 23:48 ` [PATCH 11/21] KVM: SEV: Move SEV-specific VM initialization " Sean Christopherson
2026-03-10 23:48 ` [PATCH 12/21] KVM: SEV: WARN on unhandled VM type when initializing VM Sean Christopherson
2026-04-09 5:12 ` Yan Zhao [this message]
2026-04-09 18:48 ` Sean Christopherson
2026-04-10 7:46 ` Yan Zhao
2026-04-10 15:49 ` Sean Christopherson
2026-03-10 23:48 ` [PATCH 13/21] KVM: SEV: Hide "struct kvm_sev_info" behind CONFIG_KVM_AMD_SEV=y Sean Christopherson
2026-03-10 23:48 ` [PATCH 14/21] KVM: SEV: Document that checking for SEV+ guests when reclaiming memory is "safe" Sean Christopherson
2026-03-10 23:48 ` [PATCH 15/21] KVM: SEV: Assert that kvm->lock is held when querying SEV+ support Sean Christopherson
2026-03-10 23:48 ` [PATCH 16/21] KVM: SEV: use mutex guard in snp_launch_update() Sean Christopherson
2026-03-10 23:48 ` [PATCH 17/21] KVM: SEV: use mutex guard in sev_mem_enc_ioctl() Sean Christopherson
2026-03-10 23:48 ` [PATCH 18/21] KVM: SEV: use mutex guard in sev_mem_enc_unregister_region() Sean Christopherson
2026-03-10 23:48 ` [PATCH 19/21] KVM: SEV: use mutex guard in snp_handle_guest_req() Sean Christopherson
2026-03-10 23:48 ` [PATCH 20/21] KVM: SVM: Move lock-protected allocation of SEV ASID into a separate helper Sean Christopherson
2026-03-10 23:48 ` [PATCH 21/21] KVM: SEV: Goto an existing error label if charging misc_cg for an ASID fails Sean Christopherson
2026-03-11 14:29 ` [PATCH 00/21] Fixes and lock cleanup+hardening Jethro Beekman
2026-03-12 16:03 ` Sean Christopherson
2026-04-08 0:14 ` Sean Christopherson
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=adc1IrD8uqWdaOKv@yzhao56-desk.sh.intel.com \
--to=yan.y.zhao@intel.com \
--cc=clopez@suse.de \
--cc=glider@google.com \
--cc=jethro@fortanix.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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
Powered by JetHome