From: Borislav Petkov <bp@alien8.de>
To: Punit Agrawal <punitagrawal@gmail.com>
Cc: Wei Huang <whuang2@amd.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, 14 Dec 2020 13:40:23 +0100 [thread overview]
Message-ID: <20201214124023.GA25916@zn.tnic> (raw)
In-Reply-To: <871rfvoqy7.fsf@stealth>
On Sat, Dec 12, 2020 at 08:36:48AM +0900, Punit Agrawal wrote:
> To me it suggests, that there are likely more systems from the family
> that show the characteristic described below.
Until we find a *single* system with a broken BIOS which has those
objects kaputt and then this heuristic would need an exception.
VS the clear statement from AMD that from zen3 onwards, all BIOS will be
tested. I hope they boot Linux at least before they ship.
> In all these systems, the override causes this topology information to
> be ignored - treating each core to be a separate domain. The proposed
> patch removes the override so that _PSD is taken into account.
You're still not answering my question: what does the coupling of the
SMT threads bring on those systems? Power savings? Perf improvement?
Anything palpable or measurable?
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2020-12-14 12:42 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 14:48 [RFC PATCH 0/4] Add processor to the ignore PSD override list 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
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 [this message]
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=20201214124023.GA25916@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 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.