From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756397AbYFRUZT (ORCPT ); Wed, 18 Jun 2008 16:25:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753347AbYFRUZG (ORCPT ); Wed, 18 Jun 2008 16:25:06 -0400 Received: from ogre.sisk.pl ([217.79.144.158]:45370 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752786AbYFRUZF (ORCPT ); Wed, 18 Jun 2008 16:25:05 -0400 From: "Rafael J. Wysocki" To: Pavel Machek Subject: Re: [patch 6/6] x86: add c1e aware idle function Date: Wed, 18 Jun 2008 22:26:06 +0200 User-Agent: KMail/1.9.6 (enterprise 20070904.708012) Cc: Thomas Gleixner , LKML , Ingo Molnar , Arjan van de Veen , Andreas Herrmann References: <20080610171639.551369443@linutronix.de> <20080610171712.465591661@linutronix.de> <20080618192148.GA4243@ucw.cz> In-Reply-To: <20080618192148.GA4243@ucw.cz> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200806182226.07590.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wednesday, 18 of June 2008, Pavel Machek wrote: > On Thu 2008-06-12 10:29:00, Thomas Gleixner wrote: > > C1E on AMD machines is like C3 but without control from the OS. Up to > > now we disabled the local apic timer for those machines as it stops > > when the CPU goes into C1E. This excludes those machines from high > > resolution timers / dynamic ticks, which hurts especially the X2 based > > laptops. > > > > The current boot time C1E detection has another more serious flaw: > > some BIOSes do not enable C1E until the ACPI processor module is > > loaded. This causes systems to stop working after that point. > > > > To work nicely with C1E enabled machines we use a separate idle > > function, which checks on idle entry whether C1E was enabled in the > > Interrupt Pending Message MSR. This allows us to do timer broadcasting > > Entering idle is quite a common operation, and reading MSR is quite > slow. Is it possible to do better here? > > What happens if ACPI BIOS toggles MSR on all cpus *while* we are > entering idle? This seems inherently racy... Yes, and that fits the picture I'm observing on the nx6325 (see the "linux-next: Tree for June 13: IO APIC breakage on HP nx6325" thread). Thanks, Rafael