Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755177AbYJ2UYZ (ORCPT ); Wed, 29 Oct 2008 16:24:25 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754858AbYJ2UXn (ORCPT ); Wed, 29 Oct 2008 16:23:43 -0400 Received: from smtp4.pp.htv.fi ([213.243.153.38]:59856 "EHLO smtp4.pp.htv.fi" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754846AbYJ2UXm (ORCPT ); Wed, 29 Oct 2008 16:23:42 -0400 Date: Wed, 29 Oct 2008 22:22:24 +0200 From: Adrian Bunk To: Steven Rostedt Cc: Sam Ravnborg , LKML , Ingo Molnar , Frederic Weisbecker , Abhishek Sagar , "David S. Miller" , Thomas Gleixner , Peter Zijlstra , Andrew Morton , Linus Torvalds , Steven Rostedt Subject: Re: [PATCH 01/11] ftrace: handle generic arch calls Message-ID: <20081029202224.GB1816@cs181140183.pp.htv.fi> References: <20081022184313.179487464@goodmis.org> <20081022185135.618026303@goodmis.org> <20081029190045.GC22105@uranus.ravnborg.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1794 Lines: 57 On Wed, Oct 29, 2008 at 03:24:19PM -0400, Steven Rostedt wrote: > > On Wed, 29 Oct 2008, Sam Ravnborg wrote: > > > > > > +if ($arch eq "x86") { > > > + if ($bits == 64) { > > > + $arch = "x86_64"; > > > + } else { > > > + $arch = "i386"; > > > + } > > > +} > > > + > > > if ($arch eq "x86_64") { > > > $section_regex = "Disassembly of section"; > > > $function_regex = "^([0-9a-fA-F]+)\\s+<(.*?)>:"; > > > > > > > This looks strange to my eyes. > > Why not do the more obvious: > > if ($arch eq "x86" && $bits == 64) { > > > > The change above is like trying to stick to the old i386/x86_64 > > notation. > > Trying to fix it tells me my answer to why I did it his way ;-) > > I have queued patches that will support other archs so x86 is not the > only arch that can be used here. But x86 is special, it seems to be the > only arch (that I know of, correct me if I'm wrong) that can compile with > multiple archs defined: make ARCH=x86_64, make ARCH=i386, or > make ARCH=x86. All are legit. >... The multiple ARCH settings with different semantics for them are an x86 curiosity. But the MIPS, PowerPC and s390 architectures also have unified 32bit/64bit architectures, so whatever you do will most likely also be required on these architectures. > -- Steve cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed -- 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/