Re: [PATCH v3 0/1] MR6007: ntdll: Don't use CLOCK_REALTIME_COARSE

[Gabriel Ivăncescu (＠insn)]

> BTW, one of the reason I want this is because I want count on NtDelayExecution being accurate on Wine (but not on Windows). I'm developing a frame limiter specific for Proton use and that allows me to accurately sleep without all the redundant spinning to compensate for native Windows' poor timer accuracy.

Eh, in general, that should be a red flag already. But it also contradicts the description where you said:
> CLOCK_*_COARSE only provides up to 1ms resolution at CONFIG_HZ=1000. OTOH, there are several ways to get up to 0.5ms resolution on modern Windows (high resolution waitable timers, NtSetTimerResolution with 0.5ms). This code path therefore has a possibility of behaving worse than native.

So which one is it?