linux-kernel - Re: [PATCH v3 00/11] Adjustments for preferred core detection

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <cb7fad8c-f288-410e-b380-1204b26930ad@kernel.org>
Date: Wed, 16 Oct 2024 17:06:29 -0500
From: Mario Limonciello <superm1@...nel.org>
To: Ivan Shapovalov <intelfx@...elfx.name>
Cc: bp@...en8.de, gautham.shenoy@....com, linux-acpi@...r.kernel.org,
 linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
 mario.limonciello@....com, perry.yuan@....com, rafael@...nel.org,
 x86@...nel.org
Subject: Re: [PATCH v3 00/11] Adjustments for preferred core detection

On 10/16/2024 17:03, Ivan Shapovalov wrote:
> 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?
> 

Open up a kernel Bugzilla and attach a full dmesg and all details.  You 
can CC me directly to it and I'll look into it.

Also ideally; can you please check 6.12-rc3.

> 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,