Re: [PATCH v10 6/7] x86/paravirt: add active_sched_clock to pv_time_ops

2018-06-19 Thread Thomas Gleixner
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

Re: [PATCH v10 6/7] x86/paravirt: add active_sched_clock to pv_time_ops

2018-06-19 Thread Thomas Gleixner
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

[PATCH v10 6/7] x86/paravirt: add active_sched_clock to pv_time_ops

2018-06-15 Thread Pavel Tatashin
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.

[PATCH v10 6/7] x86/paravirt: add active_sched_clock to pv_time_ops

2018-06-15 Thread Pavel Tatashin
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.