On Mon, Jan 23, 2012 at 08:15:11PM +0100, Jan Kiszka wrote: > 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.kis...@siemens.com>
That looks good - thank you for making the effort to come up with something that maps so well to the libvirt model for this concept. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
