Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752074AbbEAVmn (ORCPT ); Fri, 1 May 2015 17:42:43 -0400 Received: from mail-la0-f44.google.com ([209.85.215.44]:36155 "EHLO mail-la0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751378AbbEAVml (ORCPT ); Fri, 1 May 2015 17:42:41 -0400 MIME-Version: 1.0 In-Reply-To: <20150420071556.GB14315@gmail.com> References: <1429404795-23260-1-git-send-email-lenb@kernel.org> <20150420071556.GB14315@gmail.com> Date: Fri, 1 May 2015 14:42:39 -0700 X-Google-Sender-Auth: R5MTnDDCAqC6yAKq2rl1fIsfSQk Message-ID: Subject: Re: [PATCH 0/1] speeding up cpu_up() From: Len Brown To: Ingo Molnar Cc: X86 ML , Linux PM list , "linux-kernel@vger.kernel.org" , Borislav Petkov , Thomas Gleixner , "H. Peter Anvin" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1321 Lines: 31 On Mon, Apr 20, 2015 at 12:15 AM, Ingo Molnar wrote: > So instead of playing games with an ancient delay, I'd suggest we > install the 10 msec INIT assertion wait as a platform quirk instead, > and activate it for all CPUs/systems that we think might need it, with > a sufficiently robust and future-proof quirk cutoff condition. > > New systems won't have the quirk active and thus won't have to have > this delay configurable either. Okay, at this time, I think the quirk would apply to: 1. Intel family 5 (original pentium) -- some may actually need the quirk 2. Intel family F (pentium4) -- mostly b/c I don't want to bother finding/testing p4 3. All AMD (happy to narrow down, if somebody can speak for AMD) I'd keep the cmdline override, in case we break something, or somebody wants to optimize/test. (Though I'll update units to usec, rather than msec., so we can go below 1ms without going to 0) I don't think we need the config option, just a #define to document the quirk. What do you think? Len Brown, Intel Open Source Technology Center -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/