From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 00:50:54 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C35A81065692 for ; Wed, 9 Sep 2009 00:50:54 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 344098FC0A for ; Wed, 9 Sep 2009 00:50:53 +0000 (UTC) Received: from inchoate.gsoft.com.au (inchoate.gsoft.com.au [203.31.81.30]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id n890opTJ002759 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 9 Sep 2009 10:20:52 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: Ian Smith Date: Wed, 9 Sep 2009 10:20:48 +0930 User-Agent: KMail/1.9.10 References: <200909082209.37454.doconnor@gsoft.com.au> <20090909030624.Y89278@sola.nimnet.asn.au> In-Reply-To: <20090909030624.Y89278@sola.nimnet.asn.au> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart8884801.qQvL6L6gmr"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200909091020.51049.doconnor@gsoft.com.au> X-Spam-Score: -3.608 () ALL_TRUSTED,AWL,BAYES_00 X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: FreeBSD Stable , Henrik Friedrichsen Subject: Re: Detecting CPU throttling on over temperature X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Sep 2009 00:50:54 -0000 --nextPart8884801.qQvL6L6gmr Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wed, 9 Sep 2009, Ian Smith wrote: > > > Does anyone know if it is possible to determine if this is the > > > case? ie is there a way to be informed if throttling has > > > occurred? > > Might be easier to hack powerd.c as an existing pretty lightweight > way of monitoring CPU freq (to log or signal on detected freq lowered > by throttling, say?) even if you don't need/want it to actually vary > freq according to load, eg setting idle/busy shift factors to > 'never/always'? Hmm, that could work. It seems odd to me that there is no direct way the BIOS can notify the=20 OS it's throttling the CPU though. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart8884801.qQvL6L6gmr Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iD8DBQBKpvvq5ZPcIHs/zowRAuOsAKChwb1/uiIExkaWPthf5MagdNru5wCfakgZ pqvEk736iTlwr9s2kBQdXAU= =awGz -----END PGP SIGNATURE----- --nextPart8884801.qQvL6L6gmr--