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
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
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
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
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