-
Notifications
You must be signed in to change notification settings - Fork 88
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
print_cpuid display incorrect data for at least Cortex-A35 #43
Labels
Comments
Sounds reasonable to me. Can you make a pull request with a patch? |
bennoleslie
pushed a commit
to BreakawayConsulting/seL4_tools
that referenced
this issue
Aug 30, 2021
The existing print_cpuid function displays the incorrect value for Cortex-A35. (See issue seL4#43). This change makes CPUID determination an explicit switch statement rather than attempting to automatically determine it through masking certain bits. Note: At some level this will be a regression as it now only prints the textual id for Cortex-A35 and no other CPU. Improvements to list other CPUID mappings is welcome, unfortunately the only platform I have access to for testing is Cortex-A35.
Merged
bennoleslie
pushed a commit
to BreakawayConsulting/seL4_tools
that referenced
this issue
Aug 30, 2021
The existing print_cpuid function displays the incorrect value for Cortex-A35. (See issue seL4#43). This change makes CPUID determination an explicit switch statement rather than attempting to automatically determine it through masking certain bits. Note: At some level this will be a regression as it now only prints the textual id for Cortex-A35 and no other CPU. Improvements to list other CPUID mappings is welcome, unfortunately the only platform I have access to for testing is Cortex-A35. Signed-off-by: Ben Leslie <benno@brkawy.com>
OK. I finally made a pull request: #107 |
bennoleslie
pushed a commit
to BreakawayConsulting/seL4_tools
that referenced
this issue
Aug 30, 2021
The existing print_cpuid function displays the incorrect value for Cortex-A35. (See issue seL4#43). This change makes CPUID determination an explicit switch statement rather than attempting to automatically determine it through masking certain bits. Note: At some level this will be a regression as it now only prints the textual id for Cortex-A35 and no other CPU. Improvements to list other CPUID mappings is welcome, unfortunately the only platform I have access to for testing is Cortex-A35. Signed-off-by: Ben Leslie <benno@brkawy.com>
bennoleslie
pushed a commit
to BreakawayConsulting/seL4_tools
that referenced
this issue
Sep 2, 2021
The existing print_cpuid function displays the incorrect value for Cortex-A35. (See issue seL4#43). This change makes CPUID determination an explicit switch statement rather than attempting to automatically determine it through masking certain bits. Note: At some level this will be a regression as it now only prints the textual id for Cortex-A35 and no other CPU. Improvements to list other CPUID mappings is welcome, unfortunately the only platform I have access to for testing is Cortex-A35. Signed-off-by: Ben Leslie <benno@brkawy.com>
bennoleslie
pushed a commit
to BreakawayConsulting/seL4_tools
that referenced
this issue
Sep 2, 2021
The existing print_cpuid function displays the incorrect value for Cortex-A35. (See issue seL4#43). This change makes CPUID determination an explicit switch statement rather than attempting to automatically determine it through masking certain bits. Note: Only the Cortex-A35 case in the switch statement has been tested. Others cases are implemented from available lists only and have not been validated on real hardware. Sources: https://en.wikipedia.org/wiki/Comparison_of_ARMv8-A_cores seL4#107 (comment) Signed-off-by: Ben Leslie <benno@brkawy.com>
lsf37
pushed a commit
that referenced
this issue
Sep 2, 2021
The existing print_cpuid function displays the incorrect value for Cortex-A35. (See issue #43). This change makes CPUID determination an explicit switch statement rather than attempting to automatically determine it through masking certain bits. Note: Only the Cortex-A35 case in the switch statement has been tested. Others cases are implemented from available lists only and have not been validated on real hardware. Sources: https://en.wikipedia.org/wiki/Comparison_of_ARMv8-A_cores #107 (comment) Signed-off-by: Ben Leslie <benno@brkawy.com>
sleffler
pushed a commit
to AmbiML/sparrow-seL4_tools
that referenced
this issue
Oct 11, 2022
The existing print_cpuid function displays the incorrect value for Cortex-A35. (See issue seL4#43). This change makes CPUID determination an explicit switch statement rather than attempting to automatically determine it through masking certain bits. Note: Only the Cortex-A35 case in the switch statement has been tested. Others cases are implemented from available lists only and have not been validated on real hardware. Sources: https://en.wikipedia.org/wiki/Comparison_of_ARMv8-A_cores seL4#107 (comment) Signed-off-by: Ben Leslie <benno@brkawy.com> GitOrigin-RevId: c5f0e54
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The function
print_cpuid
incorrectly calculates the CPU name associated with the part number.The current code is:
However, the Cortex-A35
part
is0xD04
. The current logic prints that asCortex-A54
, which is obviously wrong.I think the assumptions made in this printing is just incorrect. A switch-based look up table is probably most appropriate. Something like:
But, obviously, with additional switch statements for other, supported, CPUs.
The text was updated successfully, but these errors were encountered: