Skip to content

BM/pstate: Fix balance_performance EPP check on EMR - #593

Open
abcd1234-yeah wants to merge 1 commit into
intel:mainfrom
abcd1234-yeah:fix-emr-pstate-epp
Open

BM/pstate: Fix balance_performance EPP check on EMR#593
abcd1234-yeah wants to merge 1 commit into
intel:mainfrom
abcd1234-yeah:fix-emr-pstate-epp

Conversation

@abcd1234-yeah

Copy link
Copy Markdown

Summary

intel_pstate_tests08 verifies the EPP request value after setting
energy_performance_preference to balance_performance.

The test currently expects EPP value 32 only on Sapphire Rapids
(model 143). On Emerald Rapids (model 207), it falls back to the legacy
expected value 128, but the current kernel behavior is to use 32.

The upstream Linux change 64a66f4a3c89 ("cpufreq: intel_pstate: Update
Balance performance EPP for Emerald Rapids") changed Emerald Rapids to
use the same balance_performance EPP value as Sapphire Rapids.

Update the LKVS expectation for model 207 to match the kernel behavior.

Validation

I have done:

  • git diff --check origin/main..HEAD
  • bash -n BM/pstate/intel_pstate_tests.sh
  • scripts/checkpatch.pl --strict 0001-BM-pstate-Fix-balance_performance-EPP-check-on-EMR.patch
  • Ran ./intel_pstate_tests.sh -t verify_gov_powersave_epp_balance_perf
    on an Emerald Rapids system, model 207. Passed.

The EMR run reported CPU model 207, read EPP value 32, and completed
with check_epp_req PASS.

Signed-off-by: Yijia Wang [email protected]

intel_pstate_tests08 sets energy_performance_preference to
balance_performance and then verifies the EPP request value reported by
x86_energy_perf_policy. The test currently treats only Sapphire Rapids
model 143 as using EPP 32, so Emerald Rapids model 207 falls back to the
legacy expected value 128.

The upstream Linux change 64a66f4a3c89 ("cpufreq: intel_pstate: Update
Balance performance EPP for Emerald Rapids") changed Emerald Rapids to
use the same balance_performance EPP value as Sapphire Rapids, 32. Update
the LKVS expectation for model 207 to match the kernel behavior.

Signed-off-by: Yijia Wang <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant