Return-Path: <linux-kernel-owner+willy=40w.ods.org@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S265633AbSLCUUx>; Tue, 3 Dec 2002 15:20:53 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S265636AbSLCUUx>; Tue, 3 Dec 2002 15:20:53 -0500
Received: from mg01.austin.ibm.com ([192.35.232.18]:8077 "EHLO
	mg01.austin.ibm.com") by vger.kernel.org with ESMTP
	id <S265633AbSLCUUv>; Tue, 3 Dec 2002 15:20:51 -0500
Subject: Re: [Linux-pm-devel] Re: IBM/MontaVista Dynamic Power Management
	Project
From: Hollis Blanchard <hollis@austin.ibm.com>
To: Dominik Brodowski <linux@brodo.de>
Cc: Arjan van de Ven <arjanv@redhat.com>, Bishop Brock <bcbrock@us.ibm.com>,
       linux-kernel@vger.kernel.org, cpufreq list <cpufreq@www.linux.org.uk>,
       linux-pm-devel@lists.sourceforge.net
In-Reply-To: <20021203200019.GD1340@brodo.de>
References: <OF6879354C.0478D137-ON86256C84.005CA3C0@pok.ibm.com>
	<1038938270.28176.2.camel@laptop.fenrus.com>
	<1038940024.1249.190.camel@granite.austin.ibm.com> 
	<20021203200019.GD1340@brodo.de>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature";
	boundary="=-fywVWSodTMKSpGOxfF2K"
X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) 
Date: 03 Dec 2002 14:31:12 -0600
Message-Id: <1038947473.1249.217.camel@granite.austin.ibm.com>
Mime-Version: 1.0
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 2119
Lines: 58


--=-fywVWSodTMKSpGOxfF2K
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Tue, 2002-12-03 at 14:00, Dominik Brodowski wrote:
> On Tue, Dec 03, 2002 at 12:27:03PM -0600, Hollis Blanchard wrote:
> > On Tue, 2002-12-03 at 11:57, Arjan van de Ven wrote:
> > >=20
> > > any idea if/how this will fit into the existing cross platform cpufre=
q
> > > framework ?
> >=20
> > It subsumes it, similar to Dominik's ideas in "[RFC] Dynamic Frequency
> > and Voltage Scaling Infrastructure" (on the cpufreq list). The idea is
> > that you want scaling events to be generated by the kernel rather than
> > only scaling on userland input. The paper (and Dominik's mail) give you
> > some ideas of when and why...
>=20
> So, will it basically be a "policy governor" as described in my "[RFC]" m=
ail?
> Or does it need other enhancements in the cpufreq core?=20
>=20
> BTW, have you noticed the premilinary patch I which implements most of th=
e=20
> DVS infrastructure mentioned in my mail to the cpufreq list yesterday?

Honestly I haven't had time to read it over and compare and contrast
with the IBM paper. From the sound of things though, I suspect both your
patch and the IBM code implement the same thing: an infrastructure
allowing "governors" to control dynamic scaling. The 405LP code also
includes such a governor of course. The ideas may be almost identical;
I'm not sure anyone's compared at this point. Do you have the time? ;)

-Hollis
--=20
PowerPC Linux
IBM Linux Technology Center

--=-fywVWSodTMKSpGOxfF2K
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQA97RSQ4KXmU2P6AeoRAmwyAJ44XMkaw4lflGxl8kw14ooDfrRTNgCdFWAD
BuQKi9d8noHAGFvuKZ8yfAE=
=usdH
-----END PGP SIGNATURE-----

--=-fywVWSodTMKSpGOxfF2K--

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