Date: Tue, 14 Jan 2003 13:40:01 -0800 From: Marcel Moolenaar <marcel@xcllnt.net> To: John Baldwin <jhb@FreeBSD.org> Cc: Nate Lawson <nate@root.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org, Nate Lawson <njl@FreeBSD.org> Subject: Re: cvs commit: src/sys/dev/acpica acpi_cpu.c Message-ID: <20030114214001.GA1878@dhcp01.pn.xcllnt.net> In-Reply-To: <XFMail.20030114160438.jhb@FreeBSD.org> References: <Pine.BSF.4.21.0301141210050.39326-100000@root.org> <XFMail.20030114160438.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jan 14, 2003 at 04:04:38PM -0500, John Baldwin wrote: > > >> > For the cpu throttling message, s/enabled/available > >> > >> Albeit lying. If it were just available but not enabled, then the > >> CPU wouldn't slow down when I pulled the power cord of out my laptop. > > > > But not active (until subsequent actions occur). > > What's wrong with 'enabled'? And technically, it is active. Agreed. It's enabled, not just available. The throttling happens in *reaction* to certain events. If the throttling was available but not enabled, then throttling would not happen in reaction to those events. The fact that it is a reactive feature does not mean it's not enabled when not active. Active of course means that the CPUs are currently being throttled (ie the act of throttling). -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030114214001.GA1878>