Re: [PATCH 4/7] x86/kexec: Disable kexec/kdump on platforms with TDX partial write erratum

[Edgecombe, Rick P]

On Mon, 2025-10-27 at 00:50 +0000, Huang, Kai wrote:
> > 
> > IIUC, kernel doesn't donate any of it's available memory to TDX module
> > if TDX is not actually enabled (i.e. if "kvm.intel.tdx=y" kernel
> > command line parameter is missing).
> 
> Right (for now KVM is the only in-kernel TDX user).
> 
> > 
> > Why is it unsafe to allow kexec/kdump if "kvm.intel.tdx=y" is not
> > supplied to the kernel?
> 
> It can be relaxed.  Please see the above quoted text from the changelog:
> 
>  > It's feasible to further relax this limitation, i.e., only fail kexec
>  > when TDX is actually enabled by the kernel.  But this is still a half
>  > measure compared to resetting TDX private memory so just do the simplest
>  > thing for now.

I think KVM could be re-inserted with different module params? As in, the two
in-tree users could be two separate insertions of the KVM module. That seems
like something that could easily come up in the real world, if a user re-inserts
for the purpose of enabling TDX. I think the above quote was talking about
another way of checking if it's enabled.