i#6938 sched migrate: Fix direct switch blocked_start_time #6970
Conversation
This file contains 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
Fixes a bug (discovered while testing separate runqueues) where direct switch requests with timeouts do not set blocked_start_time, resulting in re-using a prior (possibly 0) time and consequently much shorter timeouts. Reduces the default block_time_max parameter, as the bug was artificially reducing many instances and with the accurate timeout the existing defaults were no longer well-tuned. Updates unit tests. Issue: #6938
brettcoon
approved these changes
Sep 10, 2024
|
a64 failure is statecmp-fuzz #6944 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes a bug (discovered while testing separate runqueues) where direct switch requests with timeouts do not set blocked_start_time, resulting in re-using a prior (possibly 0) time and consequently much shorter timeouts.
Reduces the default block_time_max parameter, as the bug was artificially reducing many instances and with the accurate timeout the existing defaults were no longer well-tuned.
Updates unit tests.
Issue: #6938