Repository navigation
Conversation
The uncore writer skipped dies with both effective limits at 0, so limits set by a not anymore active class stayed in sysfs. A pod using a class with uncoreMinFreq left the die at that minimum after it finished. A min dropping to 0 while a max remained was skipped for the same reason. Track what was written to each die and write the hardware default back when no class requests the limit any more. The sysfs writer clamps to the hardware range, so 0 and MaxInt32 end up as the hardware min and max. Signed-off-by: Alexander Kanevskiy <alexander.kanevskiy@intel.com>
kad
force-pushed
the
fix/uncore-restore
branch
from
October 24, 2026 10:06
4aa1c92 to
6fa8e84
Compare
klihub
approved these changes
Oct 27, 2026
This branch has not been deployed
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.
The uncore writer skipped dies with both effective limits at 0, so limits set by a not anymore active class stayed in sysfs. A pod using a class with uncoreMinFreq left the die at that minimum after it finished. A min dropping to 0 while a max remained was skipped for the same reason.
Track what was written to each die and write the hardware default back when no class requests the limit any more. The sysfs writer clamps to the hardware range, so 0 and MaxInt32 end up as the hardware min and max.