Comment 25 for bug 1349883

Hi Stefan,

I looked at this a long time back (circa 2011), and things may have changed since then. See: https://forums.aws.amazon.com/thread.jspa?threadID=59753

When I looked at this last, we weren't emulating TSC and the CPUID flags that advertise invariant TSC came through. This was making the scheduler clock "stable" and printk() would use native_sched_clock() for x86, i.e. rdtscll().

I don't know how this is involved with setting up the pvclock timesource...