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

Date:	Mon, 11 Jul 2011 20:22:04 +0100
From:	Rafał Bilski <rafalbilski@...eria.pl>
To:	Harald Welte <HaraldWelte@...tech.com>,
	LKLM <linux-kernel@...r.kernel.org>
Subject: CPUFREQ: Mark e_powersaver driver as EXPERIMENTAL and DANGEROUS

Hello!

Sorry for late reply. I've been aware problem with "e_powersaver". 
Nobody ever e-mailed me :-)
So far I'm aware "e_powersaver" fully respects values given it by CPU. 
Only code added by VIA
seems to be faulty for me. As I understand ACPI P-States provide 
unstable 400MHz for system in question too.
If "e_powersaver" was based on outdated documentation I'm sorry. This 
driver was neccessary for systems with
C7 CPU's which didn't provide BIOS P-states. But it was in early and 
dark ages of first C7 CPU's.

Bye

----------------------------------------------------------------
Najwieksza baza samochodow nowych i uzywanych
Sprawdz >> http://linkint.pl/f29e3
--
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/