Jan Kiszka 4e4fa398db qdev: Introduce lost tick policy property
Potentially tick-generating timer devices will gain a common property:
lock_tick_policy. It allows to encode 4 different ways how to deal with
tick events the guest did not process in time:

discard - ignore lost ticks (e.g. if the guest compensates for them
          already)
delay   - replay all lost ticks in a row once the guest accepts them
          again
merge   - if multiple ticks are lost, all of them are merged into one
          which is replayed once the guest accepts it again
slew    - lost ticks are gradually replayed at a higher frequency than
          the original tick

Not all timer device will need to support all modes. However, all need
to accept the configuration via this common property.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2012-02-01 14:45:01 -06:00
2012-01-26 14:49:18 +01:00
2012-01-21 05:17:02 +01:00
2012-01-26 14:49:18 +01:00
2012-01-27 10:50:55 -06:00
2012-01-21 05:17:02 +01:00
2012-01-25 15:10:17 +00:00
2012-01-21 05:17:00 +01:00
2012-01-21 05:17:01 +01:00
2012-01-26 14:49:18 +01:00
2012-01-26 14:49:18 +01:00
2012-01-26 14:49:18 +01:00
2012-01-26 14:49:18 +01:00
2012-02-01 14:42:03 -06:00
2012-01-26 14:49:18 +01:00
2012-01-26 14:49:18 +01:00
2012-01-26 14:49:18 +01:00
2012-01-27 05:29:56 +00:00
2012-01-26 14:49:18 +01:00
2012-01-26 14:49:18 +01:00
2012-01-26 14:49:18 +01:00
2012-01-30 19:13:21 +00:00
2012-01-27 10:50:47 -06:00
2012-01-27 10:50:47 -06:00
2012-01-27 10:50:47 -06:00
2012-01-25 17:59:39 +00:00

Read the documentation in qemu-doc.html or on http://wiki.qemu.org

- QEMU team
Description
No description provided
Readme 404 MiB
Languages
C 82.6%
C++ 6.5%
Python 3.4%
Dylan 2.9%
Shell 1.6%
Other 2.8%