Re: [PATCH xserver 2/4] os: Use separate clockid for GetTimeInMicros()

2017-12-28 Thread Jeffrey Smith
On Wed, Dec 27, 2017 at 9:38 PM, Keith Packard wrote: > Jeffrey Smith writes: > >> GetTimeInMillis uses the CLOCK_MONOTONIC_COARSE clock if >> available and the precision is high enough. That clock is supposed >> to be more efficient to query than

Re: [PATCH xserver 2/4] os: Use separate clockid for GetTimeInMicros()

2017-12-27 Thread Keith Packard
Jeffrey Smith writes: > GetTimeInMillis uses the CLOCK_MONOTONIC_COARSE clock if > available and the precision is high enough. That clock is supposed > to be more efficient to query than CLOCK_MONOTONIC (at the cost > of being less precise). So implementing GetTimeInMillis

Re: [PATCH xserver 2/4] os: Use separate clockid for GetTimeInMicros()

2017-12-27 Thread Jeffrey Smith
On Wed, Dec 27, 2017 at 1:26 PM, Keith Packard wrote: > Jeff Smith writes: > >> Prior to commit a779fda2 (xwayland: Use the CLOCK_MONOTONIC clock), >> GetTimeInMillis() and GetTimeInMicros() had separate clockid's. As a >> part of making them available to

Re: [PATCH xserver 2/4] os: Use separate clockid for GetTimeInMicros()

2017-12-27 Thread Keith Packard
Jeff Smith writes: > Prior to commit a779fda2 (xwayland: Use the CLOCK_MONOTONIC clock), > GetTimeInMillis() and GetTimeInMicros() had separate clockid's. As a > part of making them available to ForceClockId(), that commit replaced > them with a single clockid, whose value

[PATCH xserver 2/4] os: Use separate clockid for GetTimeInMicros()

2017-12-26 Thread Jeff Smith
Prior to commit a779fda2 (xwayland: Use the CLOCK_MONOTONIC clock), GetTimeInMillis() and GetTimeInMicros() had separate clockid's. As a part of making them available to ForceClockId(), that commit replaced them with a single clockid, whose value depended on which GetTime function got called