From owner-freebsd-acpi@FreeBSD.ORG Wed Jun 27 12:22:51 2012 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5B7F510657B3; Wed, 27 Jun 2012 12:22:51 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 2F43B8FC17; Wed, 27 Jun 2012 12:22:51 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 77FD1B911; Wed, 27 Jun 2012 08:22:50 -0400 (EDT) From: John Baldwin To: Sean Bruno Date: Wed, 27 Jun 2012 08:12:46 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p17; KDE/4.5.5; amd64; ; ) References: <1340756603.2898.12.camel@powernoodle.corp.yahoo.com> In-Reply-To: <1340756603.2898.12.camel@powernoodle.corp.yahoo.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201206270812.46885.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Wed, 27 Jun 2012 08:22:50 -0400 (EDT) Cc: freebsd-acpi@freebsd.org, Andriy Gapon Subject: Re: [CFT] Sparse Cstate Support -- Its possible, that I don't know what I'm doing. X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jun 2012 12:22:51 -0000 On Tuesday, June 26, 2012 8:23:23 pm Sean Bruno wrote: > Ok, version 2 now in effect. I removed the return of BUS_PROBE_DEFAULT > and this seems to do the right thing in the cases I have. > > If there are no objections to this, I'll chuck it over into -head soonish. > > > http://people.freebsd.org/~sbruno/acpi_cpu_cstate_sparse.txt Is this for a BIOS that is reporting non-contiguous Cx states or is this a patch to let your custom Intel Cx driver work? If the latter, I would rather have the driver export a contiguous range of virtual Cx states (what ACPI actually does under the covers) rather than change our code to allow sparse ACPI Cx states. -- John Baldwin