From owner-freebsd-current@FreeBSD.ORG Sun Sep 12 08:30:47 2010 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C616D106564A; Sun, 12 Sep 2010 08:30:47 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id ACF828FC14; Sun, 12 Sep 2010 08:30:46 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id LAA24595; Sun, 12 Sep 2010 11:30:44 +0300 (EEST) (envelope-from avg@icyb.net.ua) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1OuhxU-000FiF-Fh; Sun, 12 Sep 2010 11:30:44 +0300 Message-ID: <4C8C8FB3.9060100@icyb.net.ua> Date: Sun, 12 Sep 2010 11:30:43 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.8) Gecko/20100822 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: Alexander Motin References: <4C8BCAC5.5050008@root.org> <4C8C8B64.8020907@FreeBSD.org> In-Reply-To: <4C8C8B64.8020907@FreeBSD.org> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD-Current , Norikatsu Shigemura Subject: Re: CPU C-state storange on Panasonic TOUGH BOOK CF-R9 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Sep 2010 08:30:47 -0000 on 12/09/2010 11:12 Alexander Motin said the following: > Just an idea. Limits of 100 and 1000 are defined for detection of > C-states using P_LVLx_LAT registers. Because _CST explicitly specifies > which states are available, these limitations may not apply there. I > would try to comment these checks in acpi_cpu_cx_cst() and look what > happen. At least I haven't found in ACPI 3.0 specification any latency > limits applied to _CST. Not 100% sure, but what you said does make sense. I couldn't also find any such wording in ACPI 4.0 spec. -- Andriy Gapon