From owner-freebsd-acpi@FreeBSD.ORG Tue May 6 20:56:41 2014 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 820AEFE4; Tue, 6 May 2014 20:56:41 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 57CBA286; Tue, 6 May 2014 20:56:41 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 437B6B9CB; Tue, 6 May 2014 16:56:40 -0400 (EDT) From: John Baldwin To: Adrian Chadd Subject: Re: proposal: set default lid state to S3, performance/economy Cx states to Cmax Date: Tue, 6 May 2014 16:37:29 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20140415; KDE/4.5.5; amd64; ; ) References: <201405051657.49992.jhb@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201405061637.30037.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 06 May 2014 16:56:40 -0400 (EDT) Cc: Kevin Oberman , "freebsd-acpi@freebsd.org" , "freebsd-arch@freebsd.org" X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 May 2014 20:56:41 -0000 On Tuesday, May 06, 2014 2:08:35 pm Adrian Chadd wrote: > On 5 May 2014 13:57, John Baldwin wrote: > > > The user in question found this on 9-stable with the existing defaults as the > > HPET was just plain broken on their system and that was unrelated to Cx states. > > (Rather, Cx states were only involved because worries about them are why the > > system chose to use HPET. Had Cx states been enabled by default, they would > > have had to disable those as well in addition to forcing LAPIC instead of > > HPET.) > > Hm. Sounds uncomfortable. How does Windows run on systems like this? > Do the windows drivers just disable HPET and use LAPIC or worse for > timing, and just ignore anything lower than C1? I have no idea. Maybe they use the RTC. :-/ Maybe the HPET on these systems works if you use it "sparingly". I believe OS X might have only used the HPET to provide the "missing" LAPIC wakeups when entering Cx for example. (Our current eventtimer system wants to always use whichever timer it picks, not switch off between them.) -- John Baldwin