From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030268AbXC2Pvo (ORCPT ); Thu, 29 Mar 2007 11:51:44 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030279AbXC2Pvo (ORCPT ); Thu, 29 Mar 2007 11:51:44 -0400 Received: from mx2.suse.de ([195.135.220.15]:42166 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1030268AbXC2Pvn (ORCPT ); Thu, 29 Mar 2007 11:51:43 -0400 To: "Langsdorf, Mark" Cc: "Len Brown" , "Linus Torvalds" , "Morrow, William" , "Crouse, Jordan" , "Thomas Gleixner" , "Pavel Machek" , "Ingo Molnar" , "Eric W. Biederman" , "Nick Piggin" , "Mingming Cao" , "Adrian Bunk" , "Andrew Morton" , "Linux Kernel Mailing List" , "Michal Piotrowski" , "Mariusz Kozlowski" , "Oliver Pinter" , "Sid Boyce" , "Nick Piggin" , "Jens Axboe" , "Thomas Renninger" Subject: Re: [PATCH] i386: add command line option "local_apic_timer_c2_ok" References: <200703271816.33868.lenb@kernel.org> <200703272218.50531.lenb@kernel.org> <1449F58C868D8D4E9C72945771150BDFD967BB@SAUSEXMB1.amd.com> From: Andi Kleen Date: 29 Mar 2007 18:50:09 +0200 In-Reply-To: <1449F58C868D8D4E9C72945771150BDFD967BB@SAUSEXMB1.amd.com> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org "Langsdorf, Mark" writes: > > > If we really care about using the LAPIC timer on systems with deeper > > > than C1 support, the only alternative seems to be to test > > > if it actually works or not at boot and run-time. > > > Otherwise, we wait for future hardware with guaranteed > > > not to break under any (BIOS) conditions ships, and check for that. > > > > > > Based on what I read of the HP nx6325 where the LAPIC timer > > > is breaking C1, AMD is in the same boat. > > > > The nx6325 (Turion 64 X2) exports only C1. > > I'm not sure how the conclusion was drawn that it has > > a broken lapic timer as reflected in the "nolapic_timer" patch: > > If both cores goes into C1 at the same time, the chipset > can move the processor into a C3 like state called C1e. ... and that seems to break the local APIC timer. > AMD can craft a patch to sort this out as soon as we have > an idea what the framework is going to look like. Just a snippet to detect it would be great. Then the dmi scan could be removed and replaced with that. This would be a 2.6.21 candidate imho over the DMI hack. -Andi