Re: [PATCH v1] Use CLOCK_MONOTONIC_RAW if available for get_clock().

2021-09-30 Thread Joe Tanen
Peter, Thanks for the quick response. I've informally socialized the issue and will update this thread when I get more information. That aside, I'd find using CLOCK_MONOTONIC_RAW valuable if, e.g., I wanted test an NTP daemon inside of a guest and didn't want the host providing an

Re: [PATCH v1] Use CLOCK_MONOTONIC_RAW if available for get_clock().

2021-09-30 Thread Peter Maydell
On Thu, 30 Sept 2021 at 17:04, Joe Tanen wrote: > > CLOCK_MONOTONIC_RAW provides an unadjusted system clock on some platforms, > which is closer in spirit to providing a guest with a raw hardware clock than > CLOCK_MONOTONIC. > > Using CLOCK_MONOTONIC_RAW also works around a current issue in OSX

[PATCH v1] Use CLOCK_MONOTONIC_RAW if available for get_clock().

2021-09-30 Thread Joe Tanen
CLOCK_MONOTONIC_RAW provides an unadjusted system clock on some platforms, which is closer in spirit to providing a guest with a raw hardware clock than CLOCK_MONOTONIC. Using CLOCK_MONOTONIC_RAW also works around a current issue in OSX where CLOCK_MONOTONIC has been observed to go backwards.