Re: Fixing timekeeping for rumprun/hw

  • From: Justin Cormack <justin@xxxxxxxxxxxxxxxxxxxxx>
  • To: Martin Lucina <martin@xxxxxxxxxx>, rumpkernel-users <rumpkernel-users@xxxxxxxxxxxxx>
  • Date: Fri, 19 Jun 2015 17:50:16 +0100

On 19 June 2015 at 17:42, Martin Lucina <martin@xxxxxxxxxx> wrote:

Also note that I have no idea what the stability of TSC is under KVM and
the current code makes no attempt to figure out if TSC is invariant,
constant, or anything else. So option 3) would also be a safe(r) bet in
that the PIT should "just work".

KVM has a PV clock, see summary of how it works here
https://rwmj.wordpress.com/tag/kvmclock/

Because clocks under virtualization are problematic, using this is
probably the best solution longer term.

Justin

Other related posts: