On 11/22/22 01:20, Peter Zijlstra wrote: > Either the Changelog is broken or this TDX crud is worse crap than I > thought possible, because the only way to actually meet that requirement > as stated is stop_machine(). I think the changelog is broken. I don't see anything in the TDX module spec about "the SEMACALL can run concurrently on different CPUs". Shutdown, as far as I can tell, just requires that the shutdown seamcall be run once on each CPU. Concurrency and ordering don't seem to matter at all.