From: Adrian Bunk <bunk@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Sam Ravnborg <sam@ravnborg.org>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Frederic Weisbecker <fweisbec@gmail.com>,
Abhishek Sagar <sagar.abhishek@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Steven Rostedt <srostedt@redhat.com>
Subject: Re: [PATCH 01/11] ftrace: handle generic arch calls
Date: Wed, 29 Oct 2008 22:31:33 +0200 [thread overview]
Message-ID: <20081029203133.GC1816@cs181140183.pp.htv.fi> (raw)
In-Reply-To: <alpine.DEB.1.10.0810291622050.18694@gandalf.stny.rr.com>
On Wed, Oct 29, 2008 at 04:23:34PM -0400, Steven Rostedt wrote:
>
> On Wed, 29 Oct 2008, Adrian Bunk wrote:
> > > >
> > > > 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.
> > > The trick is usually to replace use of ARCH with SRCARCH.
> >
> > That won't help - what he wants to know is whether he's on 32bit or
> > on 64bit.
>
> I will still get the "bits" parameter.
Ah, I didn't get this bit from your email.
> The issue that we are talking about
> here is that I have this ugly if statement that deals with the fact that
> we can get "x86", "x86_64" or "i386" passed in as the ARCH. I'm guessing
> if we switch ARCH to SRCARCH then we can just test against x86 and bits?
Yes.
And as a bonus you will automatically get the correct output when you'll
add support for UML.
> -- 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
next prev parent reply other threads:[~2008-10-29 20:33 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-22 18:43 [PATCH 00/11] ftrace: clean ups and fixes Steven Rostedt
2008-10-22 18:43 ` [PATCH 01/11] ftrace: handle generic arch calls Steven Rostedt
2008-10-22 18:56 ` Andrew Morton
2008-10-22 19:02 ` Steven Rostedt
2008-10-27 17:41 ` Steven Rostedt
2008-10-29 19:00 ` Sam Ravnborg
2008-10-29 19:14 ` Steven Rostedt
2008-10-29 19:24 ` Steven Rostedt
2008-10-29 19:49 ` Sam Ravnborg
2008-10-29 20:16 ` Adrian Bunk
2008-10-29 20:23 ` Steven Rostedt
2008-10-29 20:31 ` Adrian Bunk [this message]
2008-10-29 20:22 ` Adrian Bunk
2008-10-29 19:30 ` [PATCH] ftrace, kbuild: condense recordmcount.pl parameter code Steven Rostedt
2008-10-30 23:37 ` Ingo Molnar
2008-10-31 16:16 ` Sam Ravnborg
2008-10-22 18:43 ` [PATCH 02/11] ftrace: dynamic ftrace process only text section Steven Rostedt
2008-10-22 18:43 ` [PATCH 03/11] ftrace: return error on failed modified text Steven Rostedt
2008-10-22 18:55 ` Steven Rostedt
2008-10-22 18:57 ` Andrew Morton
2008-10-22 19:03 ` Steven Rostedt
2008-10-22 18:43 ` [PATCH 04/11] ftrace: comment arch ftrace code Steven Rostedt
2008-10-22 19:09 ` Andrew Morton
2008-10-22 19:16 ` Steven Rostedt
2008-10-22 19:26 ` Andrew Morton
2008-10-22 18:43 ` [PATCH 05/11] ftrace: only have ftrace_kill atomic Steven Rostedt
2008-10-22 19:11 ` Andrew Morton
2008-10-22 19:18 ` Steven Rostedt
2008-10-22 19:27 ` Andrew Morton
2008-10-22 18:43 ` [PATCH 06/11] ftrace: add ftrace warn on to disable ftrace Steven Rostedt
2008-10-22 19:12 ` Andrew Morton
2008-10-22 19:20 ` Steven Rostedt
2008-10-22 18:43 ` [PATCH 07/11] ftrace: do not trace init sections Steven Rostedt
2008-10-22 18:43 ` [PATCH 08/11] ftrace: disable dynamic ftrace for all archs that use daemon Steven Rostedt
2008-10-22 18:43 ` [PATCH 09/11] ftrace: remove daemon Steven Rostedt
2008-10-22 18:43 ` [PATCH 10/11] ftrace: remove mcount set Steven Rostedt
2008-10-22 18:43 ` [PATCH 11/11] ftrace: remove ftrace hash Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081029203133.GC1816@cs181140183.pp.htv.fi \
--to=bunk@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sagar.abhishek@gmail.com \
--cc=sam@ravnborg.org \
--cc=srostedt@redhat.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®