-
Notifications
You must be signed in to change notification settings - Fork 55
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
ppc64_cpu @ Power9 - power mode changes #48
Comments
Is this documented somewhere? We've run across this before where the meaning of the mode values has been changed from what is architected in PAPR. |
Kindly refer to IBM’s EnergyScale documentation for this at https://www.ibm.com/downloads/cas/6GZMODN3. |
Any update here? |
This is a little frustrating on our end. While the names are documented in each new processor power scale document its not really properly defined anywhere and now instead of expanding the reversed space of available bit fields to add new energy management name definitions we keep using the same 4 energy managment minor codes and changing the names with each processor iteration. We use the H_GET_EM_PARAMS hypercall in the kernel to get the status codes for the platform, group, pool, partition where each of these is a 2 byte code. Status Codes (bit offset within 2 byte field): Bits 0:5 Reserved (zero) Bits 6:8 Energy Management major code:
|
The existing interface is being replaced with Power 10. Here is the pull request for reference: #68 For previous processors that use the H_GET_EM_PARAMS call we will have to determine the processor type to map to the correct power mode names. |
https://github.com/pratiksampat/powerpc-utils/blob/H_GET_ENERGY_SCALE_INFO_v2/src/ppc64_cpu.c is doing the same wrong mapping as this is just a copy of the current code .. |
@tyreld I try to tie the provided information - current coding and your comment above about P9 P8 - from coding
P9 - from your information above
Is my understanding correct? Thx |
Power modes @ Power9 have changed:
ppc64_cpu currently reports:
The text was updated successfully, but these errors were encountered: