7.2: forward-port BORE scheduler 6.8.0 to 7.2-rc5-1 - #175
Merged
Conversation
1Naim
approved these changes
Jul 30, 2026
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
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.
BORE 6.8.0 port to 7.2-rc5
requeue_delayed_entityAPI Update:Upstream changed the function signature to include the runqueue context:
requeue_delayed_entity(struct sched_entity *se)requeue_delayed_entity(struct cfs_rq *cfs_rq, struct sched_entity *se)update_currContext Flattening:The
update_currfunction was refactored inrc5to check!entity_is_taskand return early at the very beginning.We moved
update_curr_boreoutside of the nestedif (entity_is_task)check (which was removed upstream) to the function's root level to prevent code rejection.dequeue_task_fairRealignment:Upstream replaced direct calls of
dequeue_entitiesinsidedequeue_task_fairwith__dequeue_task. The patch was adjusted to place the BORE burst-restart trigger points around this new wrapper function.place_entitySequence Reorganization:The EEVDF calculation sequence inside
place_entityshifted, causing BORE's customvslice_found:label and target context to mismatch. The patch's hunks have been realigned to insert BORE's custom wakeup logic in the correct calculation sequence.