From: Sean Christopherson <seanjc@google.com>
To: Chao Gao <chao.gao@intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "Kirill A. Shutemov" <kas@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
linux-kernel@vger.kernel.org, linux-coco@lists.linux.dev,
kvm@vger.kernel.org, Dan Williams <dan.j.williams@intel.com>,
Xin Li <xin@zytor.com>, Kai Huang <kai.huang@intel.com>,
Adrian Hunter <adrian.hunter@intel.com>
Subject: Re: [RFC PATCH 3/4] KVM: x86/tdx: Do VMXON and TDX-Module initialization during tdx_init()
Date: Mon, 13 Oct 2025 07:23:30 -0700 [thread overview]
Message-ID: <aO0LYuzdRHsB7aPj@google.com> (raw)
In-Reply-To: <aOz1X4ywkG3nG2Up@intel.com>
On Mon, Oct 13, 2025, Chao Gao wrote:
> >-static int __tdx_enable(void)
> >+static __init int tdx_enable(void)
> > {
> >+ enum cpuhp_state state;
> > int ret;
> >
> >+ if (!cpu_feature_enabled(X86_FEATURE_XSAVE)) {
> >+ pr_err("XSAVE is required for TDX\n");
> >+ return -EINVAL;
> >+ }
> >+
> >+ if (!cpu_feature_enabled(X86_FEATURE_MOVDIR64B)) {
> >+ pr_err("MOVDIR64B is required for TDX\n");
> >+ return -EINVAL;
> >+ }
> >+
> >+ if (!cpu_feature_enabled(X86_FEATURE_SELFSNOOP)) {
> >+ pr_err("Self-snoop is required for TDX\n");
> >+ return -ENODEV;
> >+ }
> >+
> >+ state = cpuhp_setup_state(CPUHP_AP_ONLINE_DYN, "virt/tdx:online",
> >+ tdx_online_cpu, tdx_offline_cpu);
> >+ if (state < 0)
> >+ return state;
> >+
> > ret = init_tdx_module();
>
> ...
>
> >@@ -1445,11 +1462,6 @@ void __init tdx_init(void)
> > return;
> > }
> >
> >-#if defined(CONFIG_ACPI) && defined(CONFIG_SUSPEND)
> >- pr_info("Disable ACPI S3. Turn off TDX in the BIOS to use ACPI S3.\n");
> >- acpi_suspend_lowlevel = NULL;
> >-#endif
> >-
> > /*
> > * Just use the first TDX KeyID as the 'global KeyID' and
> > * leave the rest for TDX guests.
> >@@ -1458,22 +1470,30 @@ void __init tdx_init(void)
> > tdx_guest_keyid_start = tdx_keyid_start + 1;
> > tdx_nr_guest_keyids = nr_tdx_keyids - 1;
> >
> >+ err = tdx_enable();
> >+ if (err)
> >+ goto err_enable;
>
> IIRC, existing TDX modules require all CPUs to have completed per-CPU
> initialization before TDMR/PAMT initialization.
>
> But at this point, APs are not online, so tdx_enable() will fail here.
Ah. Maybe invoke tdx_enable() through a subsys_initcall() then?
next prev parent reply other threads:[~2025-10-13 14:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 22:03 [RFC PATCH 0/4] KVM: x86/tdx: Have TDX handle VMXON during bringup Sean Christopherson
2025-10-10 22:03 ` [RFC PATCH 1/4] KVM: x86: Move kvm_rebooting to x86 Sean Christopherson
2025-10-10 22:04 ` [RFC PATCH 2/4] KVM: x86: Extract VMXON and EFER.SVME enablement to kernel Sean Christopherson
2025-10-13 13:20 ` Chao Gao
2025-10-13 17:49 ` Sean Christopherson
2025-10-13 22:08 ` Edgecombe, Rick P
2025-10-13 23:54 ` Sean Christopherson
2025-10-17 8:47 ` Chao Gao
2025-10-17 17:10 ` Sean Christopherson
2025-10-10 22:04 ` [RFC PATCH 3/4] KVM: x86/tdx: Do VMXON and TDX-Module initialization during tdx_init() Sean Christopherson
2025-10-13 12:49 ` Chao Gao
2025-10-13 14:23 ` Sean Christopherson [this message]
2025-10-13 19:31 ` Edgecombe, Rick P
2025-10-13 20:59 ` Sean Christopherson
2025-10-14 8:35 ` Chao Gao
2025-10-14 18:51 ` dan.j.williams
2025-10-14 19:05 ` Sean Christopherson
2025-10-14 19:44 ` Edgecombe, Rick P
2025-10-10 22:04 ` [RFC PATCH 4/4] KVM: Bury kvm_{en,dis}able_virtualization() in kvm_main.c once more Sean Christopherson
2025-10-13 22:22 ` [RFC PATCH 0/4] KVM: x86/tdx: Have TDX handle VMXON during bringup dan.j.williams
2025-10-13 23:49 ` Sean Christopherson
2025-10-14 0:18 ` dan.j.williams
2025-11-14 23:55 ` dan.j.williams
2025-10-14 2:13 ` Alexey Kardashevskiy
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=aO0LYuzdRHsB7aPj@google.com \
--to=seanjc@google.com \
--cc=adrian.hunter@intel.com \
--cc=bp@alien8.de \
--cc=chao.gao@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=kai.huang@intel.com \
--cc=kas@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xin@zytor.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