Re: [PATCH] x86/virt/tdx: Fix lockdep assertion failure in cache flush for kexec

[Edgecombe, Rick P]

On Tue, 2026-03-10 at 06:50 -0700, Sean Christopherson wrote:
> Even when that series comes along, I would rather have __this_cpu_{read|write}()
> instead of the explicit lockdep_assert_preemption_disabled().  Similar to the WARN
> about IRQs being disabled that got removed, explicitly requiring that preemption
> be disabled feels like a description of the current code, not an actual requirement.

Agreed. It's just going to confusing if the log talks about a KVM unload path
that is not there. The simpler answer is just merge this first.