From: Borislav Petkov <bp@alien8.de>
To: Wei Huang <whuang2@amd.com>
Cc: Punit Agrawal <punitagrawal@gmail.com>,
rjw@rjwysocki.net, wei.huang2@amd.com,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
x86@kernel.org
Subject: Re: [RFC PATCH 2/4] cpufreq: acpi-cpufreq: Add processor to the ignore PSD override list
Date: Mon, 7 Dec 2020 23:30:57 +0100 [thread overview]
Message-ID: <20201207223057.GJ20489@zn.tnic> (raw)
In-Reply-To: <e9b4ae11-1fe3-a660-bb65-d3ba55ffcc56@amd.com>
On Mon, Dec 07, 2020 at 04:07:52PM -0600, Wei Huang wrote:
> I think we shouldn't override zen2 if _PSD is correct. In my opinion,
> there are two approaches:
>
> * Keep override_acpi_psd()
> Let us keep the original quirk and override_acpi_psd() function. Over
> the time, people may want to add new CPUs to override_acpi_psd(). The
> maintainer may declare that only CPUs >= family 17h will be fixed, to
> avoid exploding the check-list.
>
> * Remove the quirk completely
> We can completely remove commit acd316248205 ("acpi-cpufreq: Add quirk
> to disable _PSD usage on all AMD CPUs")? I am not sure what "AMD desktop
> boards" was referring to in the original commit message of acd316248205.
> Maybe such machines aren't in use anymore.
* Third option: do not do anything. Why?
- Let sleeping dogs lie and leave the workaround acd316248205 for old
machines.
- Make a clear cut that the override is not needed from Zen3 on, i.e.,
your patch
5368512abe08 ("acpi-cpufreq: Honor _PSD table setting on new AMD CPUs")
Punit's commit message reads "...indicates that the override is not
required for Zen3 onwards, it seems that domain information can be
trusted even on certain earlier systems."
That's not nearly a justification in my book to do this on anything < Zen3.
This way you have a clear cut, you don't need to deal with adding any
more models to override_acpi_psd() and all is good.
Unless there's a better reason to skip the override on machines < Zen3
but I haven't heard any so far...
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2020-12-07 22:31 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 14:48 [RFC PATCH 0/4] " Punit Agrawal
2020-11-25 14:48 ` [RFC PATCH 1/4] cpufreq: acpi-cpufreq: Re-factor overriding ACPI PSD Punit Agrawal
2020-12-07 19:29 ` Wei Huang
2020-12-08 23:31 ` Punit Agrawal
2020-11-25 14:48 ` [RFC PATCH 2/4] cpufreq: acpi-cpufreq: Add processor to the ignore PSD override list Punit Agrawal
2020-12-07 20:20 ` Wei Huang
2020-12-07 20:26 ` Borislav Petkov
2020-12-07 22:07 ` Wei Huang
2020-12-07 22:30 ` Borislav Petkov [this message]
2020-12-08 3:44 ` Wei Huang
2020-12-08 23:21 ` Punit Agrawal
2020-12-08 23:32 ` Borislav Petkov
2020-12-11 23:36 ` Punit Agrawal
2020-12-14 12:40 ` Borislav Petkov
2020-12-14 13:27 ` Punit Agrawal
2020-12-14 14:25 ` Borislav Petkov
2020-12-17 13:27 ` Punit Agrawal
2020-11-25 14:48 ` [RFC PATCH 3/4] x86/cpu: amd: Define processor families Punit Agrawal
2020-11-30 14:00 ` Borislav Petkov
2020-12-02 14:13 ` Punit Agrawal
2020-12-02 16:57 ` Borislav Petkov
2020-11-25 14:48 ` [RFC PATCH 4/4] cpufreq: acpi-cpufreq: Use identifiers for AMD processor family Punit Agrawal
2020-11-30 14:02 ` Borislav Petkov
2020-12-02 14:30 ` Punit Agrawal
2020-12-04 22:44 ` [RFC PATCH 0/4] Add processor to the ignore PSD override list Punit Agrawal
2020-12-07 13:55 ` Rafael J. Wysocki
2020-12-08 23:25 ` Punit Agrawal
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=20201207223057.GJ20489@zn.tnic \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=punitagrawal@gmail.com \
--cc=rjw@rjwysocki.net \
--cc=wei.huang2@amd.com \
--cc=whuang2@amd.com \
--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®