Fix unused force_high_res_timers config variable - #374
Open
MagisterX wants to merge 1 commit into
Open
Conversation
Signed-off-by: MagisterX <36625965+MagisterX@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The force_high_res_timers configuration variable was implemented and parsed from the INI file, but its value was never actually used in the waitable timer hooks.
As a result, timer promotion to high-resolution was running unconditionally, completely ignoring the user's preference.
This change binds the hook logic to the actual configuration flag, allowing users to disable the feature when needed.