[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080807222642.761AF15429D@magilla.localdomain>
Date: Thu, 7 Aug 2008 15:26:42 -0700 (PDT)
From: Roland McGrath <roland@...hat.com>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Jeremy Fitzhardinge <jeremy@...p.org>,
linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
Thomas Gleixner <tglx@...utronix.de>,
Peter Zijlstra <peterz@...radead.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
David Miller <davem@...emloft.net>,
Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
Ulrich Drepper <drepper@...hat.com>,
Rusty Russell <rusty@...tcorp.com.au>,
Gregory Haskins <ghaskins@...ell.com>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
"Luis Claudio R. Goncalves" <lclaudio@...g.org>,
Clark Williams <williams@...hat.com>,
Sam Ravnborg <sam@...nborg.org>,
"Eric W. Biederman" <ebiederm@...ssion.com>
Subject: Re: [PATCH 0/5] ftrace: to kill a daemon
> This doesn't seem any less complex than what I did. With this, I would
> have to come up with another way to handle modules. This will make
> things a lot more complex.
The scheme you've implemented can apply fine to a .ko file after it's made.
They are just .o's really. It is presumably faster to do one step per
final .ko rather than many tiny ones (per source file).
That might be a benefit to doing it all at the end for vmlinux too. I
think the best way would be to have a vmlinux.o that we actually use in the
link, rather than just analyzing and discarding. Then you can just do your
existing hack on vmlinux.o before it's linked into vmlinux.
Thanks,
Roland
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists