Re: [PATCH] x86/xen/time: set ->min_delta_ticks and ->max_delta_ticks

2017-04-10 Thread Juergen Gross
On 30/03/17 22:06, Nicolai Stange wrote: > In preparation for making the clockevents core NTP correction aware, > all clockevent device drivers must set ->min_delta_ticks and > ->max_delta_ticks rather than ->min_delta_ns and ->max_delta_ns: a > clockevent device's rate is going to change

Re: [PATCH] x86/xen/time: set ->min_delta_ticks and ->max_delta_ticks

2017-04-10 Thread Juergen Gross
On 30/03/17 22:06, Nicolai Stange wrote: > In preparation for making the clockevents core NTP correction aware, > all clockevent device drivers must set ->min_delta_ticks and > ->max_delta_ticks rather than ->min_delta_ns and ->max_delta_ns: a > clockevent device's rate is going to change

Re: [PATCH] x86/xen/time: set ->min_delta_ticks and ->max_delta_ticks

2017-04-06 Thread Juergen Gross
On 30/03/17 22:06, Nicolai Stange wrote: > In preparation for making the clockevents core NTP correction aware, > all clockevent device drivers must set ->min_delta_ticks and > ->max_delta_ticks rather than ->min_delta_ns and ->max_delta_ns: a > clockevent device's rate is going to change

Re: [PATCH] x86/xen/time: set ->min_delta_ticks and ->max_delta_ticks

2017-04-06 Thread Juergen Gross
On 30/03/17 22:06, Nicolai Stange wrote: > In preparation for making the clockevents core NTP correction aware, > all clockevent device drivers must set ->min_delta_ticks and > ->max_delta_ticks rather than ->min_delta_ns and ->max_delta_ns: a > clockevent device's rate is going to change

Re: [PATCH] x86/xen/time: set ->min_delta_ticks and ->max_delta_ticks

2017-03-30 Thread Boris Ostrovsky
On 03/30/2017 04:06 PM, Nicolai Stange wrote: > In preparation for making the clockevents core NTP correction aware, > all clockevent device drivers must set ->min_delta_ticks and > ->max_delta_ticks rather than ->min_delta_ns and ->max_delta_ns: a > clockevent device's rate is going to change

Re: [PATCH] x86/xen/time: set ->min_delta_ticks and ->max_delta_ticks

2017-03-30 Thread Boris Ostrovsky
On 03/30/2017 04:06 PM, Nicolai Stange wrote: > In preparation for making the clockevents core NTP correction aware, > all clockevent device drivers must set ->min_delta_ticks and > ->max_delta_ticks rather than ->min_delta_ns and ->max_delta_ns: a > clockevent device's rate is going to change

[PATCH] x86/xen/time: set ->min_delta_ticks and ->max_delta_ticks

2017-03-30 Thread Nicolai Stange
In preparation for making the clockevents core NTP correction aware, all clockevent device drivers must set ->min_delta_ticks and ->max_delta_ticks rather than ->min_delta_ns and ->max_delta_ns: a clockevent device's rate is going to change dynamically and thus, the ratio of ns to ticks ceases to

[PATCH] x86/xen/time: set ->min_delta_ticks and ->max_delta_ticks

2017-03-30 Thread Nicolai Stange
In preparation for making the clockevents core NTP correction aware, all clockevent device drivers must set ->min_delta_ticks and ->max_delta_ticks rather than ->min_delta_ns and ->max_delta_ns: a clockevent device's rate is going to change dynamically and thus, the ratio of ns to ticks ceases to