Date: Fri, 29 Jun 2012 14:06:59 -0700 From: Sean Bruno <seanbru@yahoo-inc.com> To: John Baldwin <jhb@freebsd.org> Cc: "freebsd-acpi@freebsd.org" <freebsd-acpi@freebsd.org>, Andriy Gapon <avg@freebsd.org> Subject: Re: [CFT] Sparse Cstate Support -- Its possible, that I don't know what I'm doing. Message-ID: <1341004019.20670.1.camel@powernoodle.corp.yahoo.com> In-Reply-To: <201206270812.46885.jhb@freebsd.org> References: <1340756603.2898.12.camel@powernoodle.corp.yahoo.com> <201206270812.46885.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 2012-06-27 at 05:12 -0700, John Baldwin wrote: > 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. > This patch is for the BIOS that reports non-contiguous ACPI Cx states. e.g. C1 and C3 with no C2. The Intel Mwaits/Cx State thing is still a work in progress and not dependent on this. Sean
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1341004019.20670.1.camel>