From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: "Verma, Vishal L" <vishal.l.verma@intel.com>,
"kas@kernel.org" <kas@kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-coco@lists.linux.dev" <linux-coco@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"ak@linux.intel.com" <ak@linux.intel.com>
Subject: Re: [PATCH] x86/tdx: Remove the early #VE handler
Date: Thu, 10 Sep 2026 20:39:47 +0000 [thread overview]
Message-ID: <b41da075607d1eaa9d96eddbf3acc24502edd604.camel@intel.com> (raw)
In-Reply-To: <20260910-b4-tdx_remove_early_ve_handler-v1-1-bf47a4d360c5@intel.com>
On Thu, 2026-09-10 at 12:28 -0600, Vishal Verma wrote:
> tdx_early_handle_ve() emulates port I/O for #VEs taken before
> idt_setup_early_traps() installs the real #VE gate. Per commit
> 32e72854fa5f ("x86/tdx: Port I/O: Add early boot support"), it exists to
> support earlyprintk's serial driver.
>
> "earlyprintk=" and "earlycon=" are both early_param() handlers, so no
> console can be registered before parse_early_param(), which runs from
> setup_arch(), after idt_setup_early_traps() has replaced the early IDT.
> Nothing in the window between idt_setup_early_handler() and
> idt_setup_early_traps() does port I/O, so this emulation doesn't ever
> get called.
>
> Remove the handler. Any #VE in the early window now falls through to
> early_fixup_exception(), as it previously did for #VEs that were not I/O
> instructions.
>
> Found with the help of an LLM observing that the real IDT is installed
> before parse_early_param(). LLMs were also used to verify this. On a TDX
> guest booted with earlyprintk, a counter added to tdx_early_handle_ve()
> for testing remained 0 after boot.
The logic and history makes sense to me. I'm surprised early printk is not
useful this early.
Reviewed-by: Rick Edgecombe <rick.p.edgecombe@intel.com>
I see do_early_exception() -> handle_vc_boot_ghcb() has some early_printks().
Presumably these don't work for the same reason?
>
> Signed-off-by: Vishal Verma <vishal.l.verma@intel.com>
> Cc: Andi Kleen <ak@linux.intel.com>
> Cc: Rick Edgecombe <rick.p.edgecombe@intel.com>
> ---
> arch/x86/include/asm/tdx.h | 4 ----
> arch/x86/coco/tdx/tdx.c | 22 ----------------------
> arch/x86/kernel/head64.c | 3 ---
> 3 files changed, 29 deletions(-)
>
> diff --git a/arch/x86/include/asm/tdx.h b/arch/x86/include/asm/tdx.h
> index 89e97d5761d8..495154a7d77d 100644
> --- a/arch/x86/include/asm/tdx.h
> +++ b/arch/x86/include/asm/tdx.h
> @@ -75,8 +75,6 @@ bool tdx_handle_virt_exception(struct pt_regs *regs, struct ve_info *ve);
>
> void tdx_halt(void);
>
> -bool tdx_early_handle_ve(struct pt_regs *regs);
> -
> int tdx_mcall_get_report0(u8 *reportdata, u8 *tdreport);
>
> int tdx_mcall_extend_rtmr(u8 index, u8 *data);
> @@ -91,8 +89,6 @@ void __init tdx_dump_td_ctls(u64 td_ctls);
> static inline void tdx_early_init(void) { };
> static inline void tdx_halt(void) { };
>
> -static inline bool tdx_early_handle_ve(struct pt_regs *regs) { return false; }
> -
> #endif /* CONFIG_INTEL_TDX_GUEST */
>
> #if defined(CONFIG_KVM_GUEST) && defined(CONFIG_INTEL_TDX_GUEST)
> diff --git a/arch/x86/coco/tdx/tdx.c b/arch/x86/coco/tdx/tdx.c
> index f904a636d449..9bc78cb28710 100644
> --- a/arch/x86/coco/tdx/tdx.c
> +++ b/arch/x86/coco/tdx/tdx.c
> @@ -755,28 +755,6 @@ static int handle_io(struct pt_regs *regs, struct ve_info *ve)
> return ve_instr_len(ve);
> }
>
> -/*
> - * Early #VE exception handler. Only handles a subset of port I/O.
> - * Intended only for earlyprintk. If failed, return false.
> - */
> -__init bool tdx_early_handle_ve(struct pt_regs *regs)
> -{
> - struct ve_info ve;
> - int insn_len;
> -
> - tdx_get_ve_info(&ve);
> -
> - if (ve.exit_reason != EXIT_REASON_IO_INSTRUCTION)
> - return false;
> -
> - insn_len = handle_io(regs, &ve);
> - if (insn_len < 0)
> - return false;
> -
> - regs->ip += insn_len;
> - return true;
> -}
> -
> void tdx_get_ve_info(struct ve_info *ve)
> {
> struct tdx_module_args args = {};
> diff --git a/arch/x86/kernel/head64.c b/arch/x86/kernel/head64.c
> index fd28b53dbac5..7b8b13f45454 100644
> --- a/arch/x86/kernel/head64.c
> +++ b/arch/x86/kernel/head64.c
> @@ -166,9 +166,6 @@ void __init do_early_exception(struct pt_regs *regs, int trapnr)
> trapnr == X86_TRAP_VC && handle_vc_boot_ghcb(regs))
> return;
>
> - if (trapnr == X86_TRAP_VE && tdx_early_handle_ve(regs))
> - return;
> -
> early_fixup_exception(regs, trapnr);
> }
>
>
> ---
> base-commit: df2908090cda368b01ff43709f51890076c56157
> change-id: 20260828-b4-tdx_remove_early_ve_handler-7c1463cf0f63
>
> Best regards,
> --
> Vishal Verma <vishal.l.verma@intel.com>
>
next prev parent reply other threads:[~2026-09-10 20:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 18:28 Vishal Verma
2026-09-10 20:39 ` Edgecombe, Rick P [this message]
2026-09-11 0:15 ` Verma, Vishal L
2026-09-11 10:37 ` Kiryl Shutsemau
2026-09-11 15:24 ` Edgecombe, Rick P
2026-09-11 16:07 ` Kiryl Shutsemau
2026-09-11 17:51 ` Edgecombe, Rick P
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=b41da075607d1eaa9d96eddbf3acc24502edd604.camel@intel.com \
--to=rick.p.edgecombe@intel.com \
--cc=ak@linux.intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=kas@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=vishal.l.verma@intel.com \
--cc=x86@kernel.org \
/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®