scx_rustland_core: Move mandatory scheduler options to BPF #1778
Conversation
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
SCX_OPS_KEEP_BUILTIN_IDLE and SCX_OPS_ENQ_LAST are strictly required for scx_rustland_core to function correctly. Without them, the framework may behave incorrectly, potentially leading to runtime errors or stalls. To ensure these options are always defined, move them to BPF, instead of relying on the compat APIs. In this way, any missing definitions will result in a build-time error rather than runtime failures. Signed-off-by: Andrea Righi <[email protected]>
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.
SCX_OPS_KEEP_BUILTIN_IDLE and SCX_OPS_ENQ_LAST are strictly required for scx_rustland_core to function correctly. Without them, the framework may behave incorrectly, potentially leading to runtime errors or stalls.
To ensure these options are always defined, move them to BPF, instead of relying on the compat APIs. In this way, any missing definitions will result in a build-time error rather than runtime failures.