From: Punit Agrawal <punitagrawal@gmail.com>
To: Borislav Petkov <bp@alien8.de>
Cc: rjw@rjwysocki.net, wei.huang2@amd.com,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH 2/2] cpufreq: acpi-cpufreq: Add processor to the ignore PSD override list
Date: Sat, 12 Dec 2020 08:36:38 +0900 [thread overview]
Message-ID: <87360boqyh.fsf@stealth> (raw)
In-Reply-To: <20201210230332.GH26529@zn.tnic> (Borislav Petkov's message of "Fri, 11 Dec 2020 00:03:32 +0100")
Borislav Petkov <bp@alien8.de> writes:
> On Fri, Dec 11, 2020 at 07:56:40AM +0900, Punit Agrawal wrote:
>> Booting Linux on a Zen2 based processor (family: 0x17, model: 0x60,
>> stepping: 0x1) shows the following message in the logs -
>>
>> acpi_cpufreq: overriding BIOS provided _PSD data
>>
>> Although commit 5368512abe08 ("acpi-cpufreq: Honor _PSD table setting
>> on new AMD CPUs") indicates that the override is not required for Zen3
>> onwards, it seems that domain information can be trusted even on
>> certain earlier systems. Update the check, to skip the override for
>> Zen2 processors known to work without the override.
>>
>> Signed-off-by: Punit Agrawal <punitagrawal@gmail.com>
>> Cc: Wei Huang <wei.huang2@amd.com>
>> ---
>> drivers/cpufreq/acpi-cpufreq.c | 9 +++++++--
>> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> What about answers to those questions first?
>
> https://lkml.kernel.org/r/20201208233216.GH27920@zn.tnic
Oh.. sorry I missed that mail for some reason. Let's continue
there.
prev parent reply other threads:[~2020-12-11 23:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 22:56 [PATCH 0/2] Add processor to the ignore PSD override list Punit Agrawal
2020-12-10 22:56 ` [PATCH 1/2] cpufreq: acpi-cpufreq: Re-factor overriding ACPI PSD Punit Agrawal
2020-12-10 22:56 ` [PATCH 2/2] cpufreq: acpi-cpufreq: Add processor to the ignore PSD override list Punit Agrawal
2020-12-10 23:03 ` Borislav Petkov
2020-12-11 23:36 ` Punit Agrawal [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=87360boqyh.fsf@stealth \
--to=punitagrawal@gmail.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=wei.huang2@amd.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.