Conversation
Signed-off-by: Koichi Imai <koichi.imai.2@tier4.jp>
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.
Description
A case was identified where retrieving leaf 0x1f returned invalid values (eax, ebx, ecx, edx are all 0) even though max_leaf was 0x1f. This occurred on an Intel(R) Core(TM) i9-14900K running Linux kernel 6.5.0-44-generic kvm. Following guidance from Intel's Software Developer's Manual (Order Number: 253665-086US December 2024), I modified the implementation to use leaf 0x0b also in the cases where the upper 8 bits of ecx are invalid.
Related links
Intel's Software Developer's Manual
How was this PR tested?
On the following environment.
Notes for reviewers