From: Ivan Shapovalov <intelfx@intelfx.name>
To: Mario Limonciello <superm1@kernel.org>
Cc: bp@alien8.de, gautham.shenoy@amd.com, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
mario.limonciello@amd.com, perry.yuan@amd.com,
rafael@kernel.org, x86@kernel.org
Subject: Re: [PATCH v3 00/11] Adjustments for preferred core detection
Date: Thu, 17 Oct 2024 02:03:52 +0400 [thread overview]
Message-ID: <3b2195074d7c8fa20f93f1dc6fc25afe5dbb2909.camel@intelfx.name> (raw)
In-Reply-To: <20240905163007.1350840-1-superm1@kernel.org>
Hi,
On my desktop Zen 3 (Vermeer) system applying this series yields a new
warning message on each boot:
> Oct 16 06:20:41 kernel: Could not retrieve highest performance (-19)
As I see it, this is one of the pr_debug()s newly promoted to warnings.
Is there anything I can provide to help fix this?
Just for completeness:
```
$ cat-files /sys/devices/system/cpu/cpufreq/policy0/*
/sys/devices/system/cpu/cpufreq/policy0/affected_cpus 0
/sys/devices/system/cpu/cpufreq/policy0/amd_pstate_highest_perf 231
/sys/devices/system/cpu/cpufreq/policy0/amd_pstate_hw_prefcore enabled
/sys/devices/system/cpu/cpufreq/policy0/amd_pstate_lowest_nonlinear_freq 1746000
/sys/devices/system/cpu/cpufreq/policy0/amd_pstate_max_freq 5274000
/sys/devices/system/cpu/cpufreq/policy0/amd_pstate_prefcore_ranking 231
/sys/devices/system/cpu/cpufreq/policy0/boost 1
/sys/devices/system/cpu/cpufreq/policy0/cpuinfo_max_freq 5274000
/sys/devices/system/cpu/cpufreq/policy0/cpuinfo_min_freq 550000
/sys/devices/system/cpu/cpufreq/policy0/cpuinfo_transition_latency 0
/sys/devices/system/cpu/cpufreq/policy0/energy_performance_available_preferences default performance balance_performance balance_power power
/sys/devices/system/cpu/cpufreq/policy0/energy_performance_preference balance_performance
/sys/devices/system/cpu/cpufreq/policy0/related_cpus 0
/sys/devices/system/cpu/cpufreq/policy0/scaling_available_governors performance powersave
/sys/devices/system/cpu/cpufreq/policy0/scaling_cur_freq 1746000
/sys/devices/system/cpu/cpufreq/policy0/scaling_driver amd-pstate-epp
/sys/devices/system/cpu/cpufreq/policy0/scaling_governor powersave
/sys/devices/system/cpu/cpufreq/policy0/scaling_max_freq 5274000
/sys/devices/system/cpu/cpufreq/policy0/scaling_min_freq 1746000
/sys/devices/system/cpu/cpufreq/policy0/scaling_setspeed <unsupported>
$ grep -w cppc /proc/cpuinfo
<empty>
```
Thanks,
--
Ivan Shapovalov / intelfx /
next prev parent reply other threads:[~2024-10-16 22:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 16:29 Mario Limonciello
2024-09-05 16:29 ` [PATCH v3 01/11] x86/amd: Move amd_get_highest_perf() from amd.c to cppc.c Mario Limonciello
2024-09-05 16:29 ` [PATCH v3 02/11] ACPI: CPPC: Adjust return code for inline functions in !CONFIG_ACPI_CPPC_LIB Mario Limonciello
2024-09-05 16:29 ` [PATCH v3 03/11] x86/amd: Rename amd_get_highest_perf() to amd_get_boost_ratio_numerator() Mario Limonciello
2024-09-05 16:30 ` [PATCH v3 04/11] ACPI: CPPC: Drop check for non zero perf ratio Mario Limonciello
2024-09-05 16:30 ` [PATCH v3 05/11] ACPI: CPPC: Adjust debug messages in amd_set_max_freq_ratio() to warn Mario Limonciello
2024-09-05 16:30 ` [PATCH v3 06/11] x86/amd: Move amd_get_highest_perf() out of amd-pstate Mario Limonciello
2024-09-05 16:30 ` [PATCH v3 07/11] x86/amd: Detect preferred cores in amd_get_boost_ratio_numerator() Mario Limonciello
2024-09-05 16:30 ` [PATCH v3 08/11] cpufreq: amd-pstate: Merge amd_pstate_highest_perf_set() into amd_get_boost_ratio_numerator() Mario Limonciello
2024-09-05 16:30 ` [PATCH v3 09/11] cpufreq: amd-pstate: Optimize amd_pstate_update_limits() Mario Limonciello
2024-09-05 16:30 ` [PATCH v3 10/11] cpufreq: amd-pstate: Add documentation for `amd_pstate_hw_prefcore` Mario Limonciello
2024-09-10 10:19 ` Russell Haley
2024-09-10 16:36 ` Mario Limonciello
2024-09-05 16:30 ` [PATCH v3 11/11] amd-pstate: Add missing documentation for `amd_pstate_prefcore_ranking` Mario Limonciello
2024-10-16 22:03 ` Ivan Shapovalov [this message]
2024-10-16 22:06 ` [PATCH v3 00/11] Adjustments for preferred core detection Mario Limonciello
2024-10-16 22:19 ` Ivan Shapovalov
2024-10-17 0:18 ` Mario Limonciello
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3b2195074d7c8fa20f93f1dc6fc25afe5dbb2909.camel@intelfx.name \
--to=intelfx@intelfx.name \
--cc=bp@alien8.de \
--cc=gautham.shenoy@amd.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=perry.yuan@amd.com \
--cc=rafael@kernel.org \
--cc=superm1@kernel.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®