linux-kernel - Re: The ondemand CPUFreq code -- I hope the functionality stays

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: <1153995121.3039.43.camel@laptopd505.fenrus.org>
Date:	Thu, 27 Jul 2006 12:12:01 +0200
From:	Arjan van de Ven <arjan@...radead.org>
To:	Miles Lane <miles.lane@...il.com>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: The ondemand CPUFreq code -- I hope the functionality stays

On Thu, 2006-07-27 at 10:54 +0200, Miles Lane wrote:
> Hello,
> 
> It sounds, from comments in the discussion of CPU Hotplug locking
> problems, as though you are considering deleting the ondemand CPUFreq
> code. 

Hi,

I think you misunderstood; we are considering removing the cpu hotplug
locking (from cpufreq), not ondemand itself. ondemand itself is not a
problem in itself, it's only the hotplug locking that's an issue (and
that issue is bigger than just ondemand btw)

Greetings,
   Arjan van de Ven
-- 
if you want to mail me at work (you don't), use arjan (at) linux.intel.com

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