linux-kernel - Re: [linux-pm] cpufreq terminally broken [was Re: community PM requirements/issues and PowerOP]

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 12 Sep 2006 13:10:24 +0400
From:	"Vitaly Wool" <vitalywool@...il.com>
To:	"Pavel Machek" <pavel@....cz>
Cc:	"Mark Gross" <mgross@...ux.intel.com>,
	"Preece Scott-PREECE" <scott.preece@...orola.com>,
	"pm list" <linux-pm@...ts.osdl.org>,
	"kernel list" <linux-kernel@...r.kernel.org>
Subject: Re: [linux-pm] cpufreq terminally broken [was Re: community PM requirements/issues and PowerOP]

Pavel,

On 9/12/06, Pavel Machek <pavel@....cz> wrote:
> Can we at least try adding that, before deciding cpufreq is unsuitable
> and starting new interface? I do not think issues are nearly as big as
> you think.. (at user<->kernel interface level, anyway; you'll need big
> changes under the hood).

who talks about user <-> kernel interface level changes at the moment?!

Vitaly
-
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/