On 5 March 2012 09:08, Paolo Bonzini <pbonz...@redhat.com> wrote: > Direct usage of rt_clock should be discouraged. For RTC devices the user > cannot choose to follow the host clock with respect to NTP adjustment > and daylight savings changes. For other devices it does not provide > determinism together with -icount or qtest, and it also keeps ticking > while the machine is paused. > > This series uses rtc_clock uniformly in device models that provide RTC > functionality, and vm_clock in the omap_lpg whose ticking should be tied > to the VM running state. For consistency I'm also switching the pl031 > to rtc_clock; so far it used the vm_clock. > > v1->v2: switch omap_lpg to vm_clock > > Paolo Bonzini (5): > rtc: add -rtc clock=rt > omap: switch omap_lpg to vm_clock > arm: switch real-time clocks to rtc_clock > pl031: rearm alarm timer upon load > pl031: switch clock base to rtc_clock
I'm happy to take these into the arm-devs tree, but I'd prefer to see an ack or review from somebody who understands qemu timers first. -- PMM
