On 30/01/20 18:42, Alexander Bulekov wrote: > With QTest, is this still a concern, since there are no CPU instructions > involved? Sometimes the fork-server starts after some I/O has already > occured (eg mapping BARs and setting up VQs for virtio-net). I know we > briefly talked about threads at some point, and it seems that iothreads > may be a concern, if any are started before fork. Other than that, since > there is no TCG/CPU thread, are there any other threads that could be > a concern? > -Alex
There is a CPU thread, it just does not do MMIO. However, it may still execute code via run_on_cpu. It's quite unlikely to have the deadlock, but if it were possible to force an early start of the fork server (at the point of os_daemonize() would be ideal) it would be cleaner and it would allow reverting this patch. This is not a NACK, just some extra info. Paolo
