linux-kernel - Re: [PATCH 2/2] CPUFREQ: Mark e_powersaver driver as EXPERIMENTAL and DANGEROUS

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

Message-ID: <20090608120846.GA13328@srcf.ucam.org>
Date:	Mon, 8 Jun 2009 13:08:46 +0100
From:	Matthew Garrett <mjg@...hat.com>
To:	Harald Welte <HaraldWelte@...tech.com>
Cc:	"Michael S. Zick" <lkml@...ethan.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Duane Griffin <duaneg@...da.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Dave Jones <davej@...hat.com>
Subject: Re: [PATCH 2/2] CPUFREQ: Mark e_powersaver driver as EXPERIMENTAL
	and DANGEROUS

On Mon, Jun 08, 2009 at 06:29:36PM +0800, Harald Welte wrote:
> The e_powersaver driver for VIA's C7 CPU's needs to be marked as
> DANGEROUS as it configures the CPU to power states that are out
> of specification.
> 
> According to Centaur, all systems with C7 and Nano CPU's support
> the ACPI p-state method.  Thus, the acpi-cpufreq driver should
> be used instead.

Do we know if vendors are actually shipping with the appropriate BIOS 
tables? The number of people using e_powersaver seems to be suspiciously 
large, though perhaps that's just because the help text implied it was 
the right choice for C7.

-- 
Matthew Garrett | mjg59@...f.ucam.org
--
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/