On 24.02.2022 20:48, Andrew Cooper wrote: > In VMX operation, the handling of INIT IPIs is changed. EXIT_REASON_INIT has > nothing to do with the guest in question, simply signals that an INIT was > received. > > Ignoring the INIT is probably the wrong thing to do, but is helpful for > debugging. Crashing the domain which happens to be in context is definitely > wrong. Print an error message and continue. > > Discovered as collateral damage from when an AP triple faults on S3 resume on > Intel TigerLake platforms.
I'm afraid I don't follow the scenario, which was (only) outlined in patch 1: Why would the BSP receive INIT in this case? And it also cannot be that the INIT was received by the vCPU while running on another CPU: With APs not coming back up, it cannot have been scheduled to run there. And it would have been de-scheduled before suspending (i.e. before any INITs are sent). Jan
