Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755799AbYJMORc (ORCPT ); Mon, 13 Oct 2008 10:17:32 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753244AbYJMORX (ORCPT ); Mon, 13 Oct 2008 10:17:23 -0400 Received: from casper.infradead.org ([85.118.1.10]:38062 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752138AbYJMORX (ORCPT ); Mon, 13 Oct 2008 10:17:23 -0400 Date: Mon, 13 Oct 2008 10:17:22 -0400 From: Arjan van de Ven To: Adrian Bunk Cc: Andi Kleen , Phil Endecott , Linux Kernel Mailing List Subject: Re: [PATCH] Mention Intel Atom in Kconfig.cpu Message-ID: <20081013101722.2a1b3afa@infradead.org> In-Reply-To: <20081013140228.GG29938@cs181140183.pp.htv.fi> References: <1223895506638@dmwebmail.dmwebmail.chezphil.org> <87zll8r86h.fsf@basil.nowhere.org> <20081013091848.7dcdaaac@infradead.org> <20081013133051.GL12131@one.firstfloor.org> <20081013093014.607c5925@infradead.org> <20081013140228.GG29938@cs181140183.pp.htv.fi> Organization: Intel X-Mailer: Claws Mail 3.5.0 (GTK+ 2.12.12; i386-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-SRS-Rewrite: SMTP reverse-path rewritten from by casper.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1703 Lines: 42 On Mon, 13 Oct 2008 17:02:30 +0300 Adrian Bunk wrote: > On Mon, Oct 13, 2008 at 09:30:14AM -0400, Arjan van de Ven wrote: > > On Mon, 13 Oct 2008 15:30:51 +0200 > > Andi Kleen wrote: > > > > > > > Core2 instruction set with tune=generic is still the best to > > > > set. > > > > > > Not sure that is true. These option are mostly for the compiler. > > > > exactly, and our benchmarks show that tune=generic is best right now > > for Atom. > > (586 scheduling sounds nice, but the pipelines are rather different. > > And the benchmarks don't lie.. ;-) > > That sounds a bit dangerous since tune=generic is documented to > change the semantics between gcc versions to better fit more recent > CPUs (there's even a small difference between gcc 4.2 and gcc 4.3): > reality is that tune=generic avoids the things that are "really bad" for a wide generation of cpus; the world of x86 is such that there really are many common things that are good for the vast majority of the cpus out there (or at least neutral). Future versions of GCC might have a specific ATOM model. Until they do, tune=generic is the right thing based on tests over a few gcc versions. Yes it's a bit fluid, but no gcc isn't going to suddenly go do stupid things for currently mass-sold cpus. -- Arjan van de Ven Intel Open Source Technology Centre For development, discussion and tips for power savings, visit http://www.lesswatts.org -- 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/