-
-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DasharoSystemFeaturesUiLib: Use callbacks to update CPU Throttling Threshold #202
Conversation
1260c39
to
8a9fd05
Compare
Is it because of CVE-2024-7344? |
0820226
to
e149e1e
Compare
DasharoModulePkg/Library/DasharoSystemFeaturesUiLib/DasharoSystemFeatures.c
Show resolved
Hide resolved
This is worrisome, like there is a memory issue that will now affect something else since a field has been removed (e.g., |
I think it has to do with how |
…reshold For some reason the CPU Throttling Threshold dsiplayed negative value when user changed CPU throttling, exited Power Management Options menu, went back to front page and then entered Power Management Options menu again. Always calculate the threshold based on PCD and current throttling offset value. Add interactive flag to the options and patch the value in the callback. Signed-off-by: Michał Żygowski <michal.zygowski@3mdeb.com>
e149e1e
to
27e4a00
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OVMF seems to work the same with and without these changes (variables are updated correctly), so seems like they at least don't break anything.
For some reason the CPU Throttling Threshold dsiplayed negative value when user changed CPU throttling, exited Power Management Options menu, went back to front page and then entered Power Management Options menu again.
Always calculate the threshold based on PCD and current throttling offset value. Add interactive flag to the options and patch the value in the callback.