diff options
author | Jan Kiszka <jan.kiszka@siemens.com> | 2009-09-15 13:36:04 +0200 |
---|---|---|
committer | Anthony Liguori <aliguori@us.ibm.com> | 2009-10-05 09:32:45 -0500 |
commit | 21d5d12bb0ad4de7cc92a7a2d018e7ec0f9fd148 (patch) | |
tree | 3297270a5b65d8d59d8e114d7fe3105e1330dffa /VERSION | |
parent | f64382bad849a16208d30988ef28d5e7375099da (diff) | |
download | hqemu-21d5d12bb0ad4de7cc92a7a2d018e7ec0f9fd148.zip hqemu-21d5d12bb0ad4de7cc92a7a2d018e7ec0f9fd148.tar.gz |
Introduce QEMU_CLOCK_HOST
Despite its name QEMU_CLOCK_REALTIME is (normally) not using
CLOCK_REALTIME / the host system time as base. In order to allow also
non-trivial RTC emulations (MC146818) to follow the host time instead of
the virtual guest time, introduce the new clock type QEMU_CLOCK_HOST. It
is unconditionally based on CLOCK_REALTIME, thus will follow system time
changes of the host.
The only limitation of its current implementation is that pending
host_clock timers may not fire early if the host time is pushed forward
beyond their expiry. So far no urgent need to overcome this limitation
was identified, so it's left as simple as it is (expiry on next alarm
timer tick).
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Diffstat (limited to 'VERSION')
0 files changed, 0 insertions, 0 deletions