Am 12.06.2012 10:24, schrieb Andreas Färber:
Am 29.05.2012 15:35, schrieb Stefano Stabellini:
qemu_rearm_alarm_timer partially duplicates the code in
qemu_next_alarm_deadline to figure out if it needs to rearm the timer.
If it calls qemu_next_alarm_deadline, it always rearms the timer even if
Am 12.06.2012 15:32, schrieb Stefano Stabellini:
On Tue, 12 Jun 2012, Andreas Färber wrote:
Am 12.06.2012 14:37, schrieb Stefano Stabellini:
On Tue, 12 Jun 2012, Andreas Färber wrote:
Am 12.06.2012 10:24, schrieb Andreas Färber:
Am 29.05.2012 15:35, schrieb Stefano Stabellini:
The
Am 29.05.2012 15:35, schrieb Stefano Stabellini:
qemu_rearm_alarm_timer partially duplicates the code in
qemu_next_alarm_deadline to figure out if it needs to rearm the timer.
If it calls qemu_next_alarm_deadline, it always rearms the timer even if
the next deadline is INT64_MAX.
This patch
Am 12.06.2012 10:24, schrieb Andreas Färber:
Am 29.05.2012 15:35, schrieb Stefano Stabellini:
The check-qtest-i386 qemu-system-i386 process now hangs at ~98% CPU,
just as with my INT64_MAX hack before. How would I best debug this qtest
scenario, and what should I be looking for? Since my 1.1
On Tue, 12 Jun 2012, Andreas Färber wrote:
Am 12.06.2012 10:24, schrieb Andreas Färber:
Am 29.05.2012 15:35, schrieb Stefano Stabellini:
The check-qtest-i386 qemu-system-i386 process now hangs at ~98% CPU,
Does this mean that increasing the timeout caused a busy loop somewhere
in the test?
Am 12.06.2012 14:37, schrieb Stefano Stabellini:
On Tue, 12 Jun 2012, Andreas Färber wrote:
Am 12.06.2012 10:24, schrieb Andreas Färber:
Am 29.05.2012 15:35, schrieb Stefano Stabellini:
The check-qtest-i386 qemu-system-i386 process now hangs at ~98% CPU,
Does this mean that increasing the
On Tue, 12 Jun 2012, Andreas Färber wrote:
Am 12.06.2012 14:37, schrieb Stefano Stabellini:
On Tue, 12 Jun 2012, Andreas Färber wrote:
Am 12.06.2012 10:24, schrieb Andreas Färber:
Am 29.05.2012 15:35, schrieb Stefano Stabellini:
The check-qtest-i386 qemu-system-i386 process now hangs at
qemu_rearm_alarm_timer partially duplicates the code in
qemu_next_alarm_deadline to figure out if it needs to rearm the timer.
If it calls qemu_next_alarm_deadline, it always rearms the timer even if
the next deadline is INT64_MAX.
This patch simplifies the behavior of qemu_rearm_alarm_timer and