On 24/02/2016 20:38, Andy Lutomirski wrote: > If the master clock accurately exposed CLOCK_MONOTONIC_RAW or > CLOCK_MONOTONIC (I much prefer the latter), then it would be fine > across suspend/resume. Here we already have a conflict... Owen says he prefers the master clock to expose the (stable) TSC, you say you prefer CLOCK_MONOTONIC. I for one _thought_ CLOCK_MONOTONIC would have been my choice, but I'm not so sure about it and I'm also not sure it's possible to do it efficiently. The mult/shift/offset tuple potentially can change every tick, and it would be bad to do such an update #vms times per tick (or worse, #vcpus times per tick). Paolo -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
