linux-kernel - Re: [PATCH 2/8 v2] acpi-cpufreq: Add quirk to disable

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-next>] [day] [month] [year] [list]

Message-ID: <5056D420.80808@amd.com>
Date:	Mon, 17 Sep 2012 09:41:20 +0200
From:	Andre Przywara <andre.przywara@....com>
To:	Konrad Rzeszutek Wilk <konrad@...nel.org>
CC:	Andreas Herrmann <andreas.herrmann3@....com>,
	Thomas Renninger <trenn@...e.de>,
	"Rafael J. Wysocki" <rjw@...k.pl>, <cpufreq@...r.kernel.org>,
	<linux-pm@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
	Matthew Garret <mjg@...hat.com>
Subject: Re: [PATCH 2/8 v2] acpi-cpufreq: Add quirk to disable _PSD usage
 on all AMD CPUs

On 09/15/2012 01:20 PM, Konrad Rzeszutek Wilk wrote:
>
> On Sep 4, 2012 4:26 AM, "Andre Przywara" <andre.przywara@....com
> <mailto:andre.przywara@....com>> wrote:
>  >
>  > To workaround some Windows specific behavior, the ACPI _PSD table
>  > on AMD desktop boards advertises all cores as dependent, meaning
>  > that they all can only use the same P-state. acpi-cpufreq strictly
>  > obeys this description, instantiating one CPU only and symlinking
>  > the others. But the hardware can have distinct frequencies for each
>  > core and powernow-k8 did it that way.
>  > So, in order to use the hardware to its full potential and keep the
>  > original powernow-k8 behavior, lets override the _PSD table setting
>  > on AMD hardware.
>
> Can you tell on which motherboards this different freq on cores can be
> exposed?

Actually I think the motherboard is not the limiting factor here.
Per-core P-states are possible on AMD Family 10h and greater CPUs, so 
Phenoms/Barcelona and beyond. You may need an AM2+/AM3 board, though. 
Fam10h CPUs run in some older AM2-only boards, but the power-management 
capabilities may be limited here. This definitely applies to the voltage 
(single power plane only), but the older BIOS on these boards may limit 
the frequency switching also.

The actual reason for this patch is the (Fam10h) BKDG [1] recommendation 
in chapter 2.4.2.13.4 _PSD (P-State Dependency). There advertising only 
one possible P-state per package is recommended - for desktop CPUs 
(which are supposed to run Windows ;-)
This was to overcome some nasty interaction between the Windows 
scheduler and their version of the ondemand governor.

Regards,
Andre.

[1] http://support.amd.com/us/Processor_TechDocs/31116.pdf

-- 
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/