aboutsummaryrefslogtreecommitdiff
path: root/block.h
diff options
context:
space:
mode:
authoraliguori <aliguori@c046a42c-6fe2-441c-8c8c-71466251a162>2008-11-25 17:26:09 +0000
committeraliguori <aliguori@c046a42c-6fe2-441c-8c8c-71466251a162>2008-11-25 17:26:09 +0000
commit357c692cca6614ac3583ca39b710a9888a673785 (patch)
treee7248265a2218fae2d0f5cb5612681e3efa725ea /block.h
parent9c99d2ab0206efad7310b26a3eee14f6f464532a (diff)
downloadqemu-357c692cca6614ac3583ca39b710a9888a673785.zip
qemu-357c692cca6614ac3583ca39b710a9888a673785.tar.gz
qemu-357c692cca6614ac3583ca39b710a9888a673785.tar.bz2
Revert r5636 to fix icount on hosts w/o high-res clocks
Changeset r5636 changed the timers to run in the alarm callback. The alarm callback can only be called as frequently as the host alarm timer fires. For older Linux hosts and possibly non-Linux hosts, this can be as high as a 1ms granularity. icount calculates the select timeout based on the next deadline and select is usually capable of sleeping for a short period of time than alarm timer granularity. This means that changing the timer callbacks to be based on alarm firing caused timers to fire much later than they ought to when using icount. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@5796 c046a42c-6fe2-441c-8c8c-71466251a162
Diffstat (limited to 'block.h')
0 files changed, 0 insertions, 0 deletions