On 16/02/2015 13:26, Pavel Dovgaluk wrote: >>> > > I think in this case there are no events at all - just reading timers >>> > > values >>> > > that were made while recording. >>> > > We have to replay these reads by waking iothread. >> > >> > I think the right place for this is in replay_read_next_clock then. > It doesn't fit. Log file is not read until all instructions are executed. > And the next read from the file should be performed by iothread which should > be notified and waked up.
I still don't understand. If you're getting EXCP_INTERRUPT it means: 1) that cpu_signal was called 2) in turn this means that qemu_cpu_kick was called 3) in turn this means that the iothread is trying to run via qemu_mutex_lock_iothread (the iothread_requesting_mutex stuff). So why do you need an explicit qemu_notify_event? Paolo
