On Fri, 2022-03-11 at 18:38 +0100, Eric Farman wrote: > When stopping a CPU, kvm-unit-tests serializes/waits for everything > to finish, in order to get a consistent result whenever those > functions are used. > > But to test the SIGP STOP itself, these additional measures could > mask other problems. For example, did the STOP work, or is the CPU > still operating? > > Let's create a non-waiting SIGP STOP and use it here, to ensure that > the CPU is correctly stopped. A smp_cpu_stopped() call will still > be used to see that the SIGP STOP has been processed, and the state > of the CPU can be used to determine whether the test passes/fails. > > Signed-off-by: Eric Farman <farman@xxxxxxxxxxxxx> > Reviewed-by: Claudio Imbrenda <imbrenda@xxxxxxxxxxxxx> Reviewed-by: Nico Boehr <nrb@xxxxxxxxxxxxx>
