Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754685AbYJ2TYa (ORCPT ); Wed, 29 Oct 2008 15:24:30 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753310AbYJ2TYW (ORCPT ); Wed, 29 Oct 2008 15:24:22 -0400 Received: from hrndva-omtalb.mail.rr.com ([71.74.56.124]:63731 "EHLO hrndva-omtalb.mail.rr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752687AbYJ2TYV (ORCPT ); Wed, 29 Oct 2008 15:24:21 -0400 Date: Wed, 29 Oct 2008 15:24:19 -0400 (EDT) From: Steven Rostedt X-X-Sender: rostedt@gandalf.stny.rr.com To: Sam Ravnborg cc: LKML , Ingo Molnar , Frederic Weisbecker , Abhishek Sagar , "David S. Miller" , Thomas Gleixner , Peter Zijlstra , Andrew Morton , Linus Torvalds , Steven Rostedt , Adrian Bunk Subject: Re: [PATCH 01/11] ftrace: handle generic arch calls In-Reply-To: <20081029190045.GC22105@uranus.ravnborg.org> Message-ID: References: <20081022184313.179487464@goodmis.org> <20081022185135.618026303@goodmis.org> <20081029190045.GC22105@uranus.ravnborg.org> User-Agent: Alpine 1.10 (DEB 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1688 Lines: 50 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. Now how do we handle this. I've been fine for all my testing to do just x86_64 and i386 because a normal make of x86 will use automatically set ARCH to i386 or x86_64 depending on the build. But then Adrian Bunk pointed out that "make ARCH=x86" fails. Now I need to add a case for x86, but still allow for x86_64 or i386 being passed in. Since x86 is the ambiguous case, I made it the one that would be converted to i386 or x86_64 since those could be passed in directly. Seems that the best approach is still what is there :-/ -- Steve -- 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/