From: Mario Limonciello <superm1@kernel.org>
To: Ivan Shapovalov <intelfx@intelfx.name>
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: Wed, 16 Oct 2024 19:18:34 -0500 [thread overview]
Message-ID: <2ae2c852-6ac2-428d-8a65-496565be7ed0@kernel.org> (raw)
In-Reply-To: <ed2a3efcb08af8286a5821acea8302164f0b0a35.camel@intelfx.name>
On 10/16/24 17:19, Ivan Shapovalov wrote:
> On 2024-10-16 at 17:06 -0500, Mario Limonciello wrote:
>> 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.
>>
>
> Alright, I'll do that once I build and test the -rc.
>
> Besides dmesg+config+cpuinfo, are there any other details that you
> would like to see there?
>
> Thanks,
>>
That's fine for now. Depending on what we find we might want to look at
an acpidump too.
prev parent reply other threads:[~2024-10-17 0:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 16:29 [PATCH v3 00/11] Adjustments for preferred core detection 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 ` [PATCH v3 00/11] Adjustments for preferred core detection Ivan Shapovalov
2024-10-16 22:06 ` Mario Limonciello
2024-10-16 22:19 ` Ivan Shapovalov
2024-10-17 0:18 ` Mario Limonciello [this message]
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=2ae2c852-6ac2-428d-8a65-496565be7ed0@kernel.org \
--to=superm1@kernel.org \
--cc=bp@alien8.de \
--cc=gautham.shenoy@amd.com \
--cc=intelfx@intelfx.name \
--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=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;
as well as URLs for NNTP newsgroup(s).