From owner-freebsd-acpi@FreeBSD.ORG  Wed Oct  3 16:21:41 2012
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
Delivered-To: freebsd-acpi@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 6DC7A106564A;
	Wed,  3 Oct 2012 16:21:41 +0000 (UTC)
	(envelope-from seanbru@yahoo-inc.com)
Received: from mrout2-b.corp.bf1.yahoo.com (mrout2-b.corp.bf1.yahoo.com
	[98.139.253.105])
	by mx1.freebsd.org (Postfix) with ESMTP id 249278FC12;
	Wed,  3 Oct 2012 16:21:40 +0000 (UTC)
Received: from [IPv6:::1] (rideseveral.corp.yahoo.com [10.73.160.231])
	by mrout2-b.corp.bf1.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id
	q93GL6mZ009136; Wed, 3 Oct 2012 09:21:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com;
	s=cobra; t=1349281268;
	bh=m0izu1CzRooeeXUFV0PE5fFj+KoS/nHHUF1n5MtP55E=;
	h=Subject:From:To:Cc:In-Reply-To:References:Content-Type:Date:
	Message-ID:Mime-Version:Content-Transfer-Encoding;
	b=vbKUCTB/XD5l9Mltj1wn2NXpIbjOK6Y4GzJdd9KatZrgcrjzu8eQAzPK9u8kFGsug
	UhOzp2XYMR7+sqrDbxzWiehiHGOAg0vq4O8kX4Dp1BLaxsfTio8eDD4qPHQ+80UdjR
	Zs+9PuqjrUVYeEkWJhO0q9glJJCVY4gfjqTr3FCM=
From: Sean Bruno <seanbru@yahoo-inc.com>
To: Andriy Gapon <avg@FreeBSD.org>
In-Reply-To: <506C38CE.4090400@FreeBSD.org>
References: <504EDBEB.6010104@FreeBSD.org>
	<1349198313.4246.3.camel@powernoodle.corp.yahoo.com>
	<506C38CE.4090400@FreeBSD.org>
Content-Type: text/plain; charset="UTF-8"
Date: Wed, 03 Oct 2012 09:21:06 -0700
Message-ID: <1349281266.13749.0.camel@powernoodle.corp.yahoo.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port 
Content-Transfer-Encoding: 7bit
X-Milter-Version: master.31+4-gbc07cd5+
X-CLX-ID: 281267004
Cc: "sbruno@FreeBSD.org" <sbruno@FreeBSD.org>,
	"freebsd-acpi@freebsd.org" <freebsd-acpi@FreeBSD.org>
Subject: Re: notify userland about C-state changes
X-BeenThere: freebsd-acpi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
	<mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
	<mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Oct 2012 16:21:41 -0000

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?


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

Sean