[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20081023133256.926296694@goodmis.org>
Date: Thu, 23 Oct 2008 09:32:56 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: linux-kernel@...r.kernel.org
Cc: Ingo Molnar <mingo@...e.hu>,
Frederic Weisbecker <fweisbec@...il.com>,
Abhishek Sagar <sagar.abhishek@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Thomas Gleixner <tglx@...utronix.de>,
Peter Zijlstra <peterz@...radead.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Wenji Huang <wenji.huang@...cle.com>
Subject: [PATCH 00/12 v3] ftrace: clean ups and fixes
[
Changes since v2:
Typo corrections suggested by Wenji Huang.
Removed adding notrace to init sections. Right now it should not
be an issue. If we deem that it is, we can add the patch later.
It's a performance patch, but I have yet to measure if the improvement
is even measurable.
]
This is a series of patches to make ftrace more robust and clean ups.
The first couple of patches fix the recordmount.pl script and changes
it to only record the .text section functions. This means that
the init sections will not be processed.
A FTRACE_WARN_ON is added to change all WARN_ONS to not only print a
warning, but also to disable ftrace as well.
The later patches are a bit more drastic. Since the daemon is error prone,
I stripped it out. In doing so, I have to disable dynamic ftrace from all
archs that use it. The archs can get dynamic ftrace reenabled when they
are ported to the recordmcount.pl method. (Arch maintainers, please contact
me if you want help. I can do it with some information about your arch).
Since the hash was created to work with the daemon, that too was stripped
out, making the remaining code smaller and cleaner. The kprobe hooks
in ftrace may need to be reworked.
Thanks goes to Andrew Morton for his comments on the code as well as
the spelling corrections made by Wenji Huang.
-- Steve
--
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