Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262268AbTINANz (ORCPT ); Sat, 13 Sep 2003 20:13:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262269AbTINANz (ORCPT ); Sat, 13 Sep 2003 20:13:55 -0400 Received: from [209.195.52.120] ([209.195.52.120]:30443 "HELO warden2.diginsite.com") by vger.kernel.org with SMTP id S262268AbTINANy (ORCPT ); Sat, 13 Sep 2003 20:13:54 -0400 From: David Lang To: Andi Kleen Cc: Adrian Bunk , linux-kernel@vger.kernel.org, Dave Jones , linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk Date: Sat, 13 Sep 2003 17:10:27 -0700 (PDT) Subject: Re: RFC: [2.6 patch] better i386 CPU selection In-Reply-To: Message-ID: References: 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 Content-Length: 1204 Lines: 28 On Sun, 14 Sep 2003, Andi Kleen wrote: > Adrian Bunk writes: > > > > I don't like the current user interface that says "if you want to > > support both an Athlon and a Pentium 4 in your kernel use the Pentium III > > option. And for better optimization, also check the "generic" option". > > The big issue with your ifdefing of workarounds is that it causes subtle > support problems. A lot of settings for specific CPUs boot and work > fine on other CPUs (possibly with small performance impact, but they're > rarely noticeable without explicit benchmarking). Just when you don't > include the workarounds for the bugs on these other CPUs it will boot and > even run, but fail mysteriously once a month. And that would be a support > nightmare. > it sounds like a nessasary part of this patch would be to detect the CPU type and complain VERY loudly if it's not one supported by the build. This is probably a good idea anyway. David Lang - 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/