On Fri, 15 Jun 2018, Pavel Tatashin wrote:
> Early boot clock might differ from the clock that is used later on,
> therefore add a new field to pv_time_ops, that shows currently active
> clock. If platform supports early boot clock, this field will be changed
> to use that clock early in boot, and later will be replaced with the
> permanent clock.
I'm not seeing why this is required. If a hypervisor provides a
sched_clock() override then it's not the kernels problem to make sure that
it is usable.
Thanks,
tglx
