https://bugs.winehq.org/show_bug.cgi?id=51857 --- Comment #6 from Idan Sheinberg <ishinberg0(a)gmail.com> --- (In reply to Zebediah Figura from comment #5)
It's going to be a hard sell to include anything like that upstream. The whole point of having multiple clock sources is that there's a tradeoff between measurement speed and clock resolution. Our current behaviour matches Windows, and there would be a performance penalty associated with using a higher-resolution clock source for NtQuerySystemTime.
Typically we don't include such optional behaviour, either. What little configuration there is in Wine is usually for working around bugs or API mismatches. The maintenance cost would be too high otherwise. Is it feasible for you to use a local patch or shim instead?
I understand what you are saying, and agree. We'll use a patch when building wine to revert this issue. 10x Idan -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.