On 04/05/2012 10:00 AM, Peter Portante wrote:
Basically, the main wait loop calls qemu_run_all_timers() unconditionally. The
first thing this routine used to do is to see if a timer had been serviced,
and then reset the loop timeout to the next deadline.
However, the new deadlines had not been c
On 04/12/2012 03:56 PM, Paolo Bonzini wrote:
Il 12/04/2012 22:55, Anthony Liguori ha scritto:
It makes sense to me but since this is a subtle change, Paolo, could you
also take a look at this change?
It looks fine, Peter and I already looked at the patch prior to his
submitting.
Thanks. I'l
Il 12/04/2012 22:55, Anthony Liguori ha scritto:
> It makes sense to me but since this is a subtle change, Paolo, could you
> also take a look at this change?
It looks fine, Peter and I already looked at the patch prior to his
submitting.
> Reviewed-by: Anthony Liguori
Paolo
On 04/05/2012 10:00 AM, Peter Portante wrote:
Basically, the main wait loop calls qemu_run_all_timers() unconditionally. The
first thing this routine used to do is to see if a timer had been serviced,
and then reset the loop timeout to the next deadline.
However, the new deadlines had not been c
Basically, the main wait loop calls qemu_run_all_timers() unconditionally. The
first thing this routine used to do is to see if a timer had been serviced,
and then reset the loop timeout to the next deadline.
However, the new deadlines had not been calculated at that point, as
qemu_run_timers() ha
