On Sat, Sep 18, 2010 at 02:38:12PM -1000, Zachary Amsden wrote: > If preempted after kvmclock values are updated, but before hardware > virtualization is entered, the last tsc time as read by the guest is > never set. It underflows the next time kvmclock is updated if there > has not yet been a successful entry / exit into hardware virt. > > Fix this by simply setting last_tsc to the newly read tsc value so > that any computed nsec advance of kvmclock is nulled. > > Signed-off-by: Zachary Amsden <[email protected]>
Applied, thanks. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
