linux-kernel - Re: [PATCH v3 4/6] x86/virt/tdx: Remove the !KEXEC

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4f8688425ae2c436c407f5a3c987b9e9bbc6a543.camel@intel.com>
Date: Thu, 26 Jun 2025 18:49:41 +0000
From: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>
To: "Hansen, Dave" <dave.hansen@...el.com>, "Huang, Kai"
	<kai.huang@...el.com>, "bp@...en8.de" <bp@...en8.de>, "peterz@...radead.org"
	<peterz@...radead.org>, "hpa@...or.com" <hpa@...or.com>, "mingo@...hat.com"
	<mingo@...hat.com>, "tglx@...utronix.de" <tglx@...utronix.de>,
	"thomas.lendacky@....com" <thomas.lendacky@....com>
CC: "seanjc@...gle.com" <seanjc@...gle.com>, "x86@...nel.org"
	<x86@...nel.org>, "sagis@...gle.com" <sagis@...gle.com>, "Chatre, Reinette"
	<reinette.chatre@...el.com>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>, "kirill.shutemov@...ux.intel.com"
	<kirill.shutemov@...ux.intel.com>, "Williams, Dan J"
	<dan.j.williams@...el.com>, "kvm@...r.kernel.org" <kvm@...r.kernel.org>,
	"pbonzini@...hat.com" <pbonzini@...hat.com>, "Yamahata, Isaku"
	<isaku.yamahata@...el.com>, "ashish.kalra@....com" <ashish.kalra@....com>,
	"Chen, Farrah" <farrah.chen@...el.com>, "nik.borisov@...e.com"
	<nik.borisov@...e.com>
Subject: Re: [PATCH v3 4/6] x86/virt/tdx: Remove the !KEXEC_CORE dependency

On Thu, 2025-06-26 at 22:48 +1200, Kai Huang wrote:
> During kexec it is now guaranteed that all dirty cachelines of TDX
> private memory are flushed before jumping to the new kernel.  The TDX
> private memory from the old kernel will remain as TDX private memory in
> the new kernel, but it is OK because kernel read/write to TDX private
> memory will never cause machine check, except on the platforms with the
> TDX partial write erratum, which has already been handled.
> 
> It is safe to allow kexec to work together with TDX now.  Remove the
> !KEXEC_CORE dependency.
> 
> Signed-off-by: Kai Huang <kai.huang@...el.com>
> Tested-by: Farrah Chen <farrah.chen@...el.com>

Reviewed-by: Rick Edgecombe <rick.p.edgecombe@...el.com>