Date: Wed, 03 Oct 2012 19:24:06 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: Sean Bruno <seanbru@yahoo-inc.com> Cc: "sbruno@FreeBSD.org" <sbruno@FreeBSD.org>, "freebsd-acpi@freebsd.org" <freebsd-acpi@FreeBSD.org> Subject: Re: notify userland about C-state changes Message-ID: <506C66A6.4070003@FreeBSD.org> In-Reply-To: <1349281266.13749.0.camel@powernoodle.corp.yahoo.com> References: <504EDBEB.6010104@FreeBSD.org> <1349198313.4246.3.camel@powernoodle.corp.yahoo.com> <506C38CE.4090400@FreeBSD.org> <1349281266.13749.0.camel@powernoodle.corp.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
on 03/10/2012 19:21 Sean Bruno said the following: > On Wed, 2012-10-03 at 06:08 -0700, Andriy Gapon wrote: >>> >>> So quick question, does this happen a lot on a system with a >> sporadic >>> workload? Does this introduce overhead to the system to service the >>> notification requests? >> >> I am not sure who can answer this question. It is up to ACPI platform >> to decide >> when it changes _available C-states_. OS doesn't have control over >> that. >> > Hrm ... what changes to the machine would make this happen while the > machine is running? things like the switching from battery to line > power? Yes. Or something else [?] of similar nature/effect. >> P.S. I hope you haven't confused this notification for a notification >> about >> _current_ C-state changing. > > I did have it confused. Thanks for putting this note in. OK :-) -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?506C66A6.4070003>