public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: 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>,
	Wenji Huang <wenji.huang@oracle.com>
Subject: [PATCH 00/12 v3] ftrace: clean ups and fixes
Date: Thu, 23 Oct 2008 09:32:56 -0400	[thread overview]
Message-ID: <20081023133256.926296694@goodmis.org> (raw)

[
  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


             reply	other threads:[~2008-10-23 13:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-23 13:32 Steven Rostedt [this message]
2008-10-23 13:32 ` [PATCH 01/12 v3] ftrace: handle generic arch calls Steven Rostedt
2008-10-23 13:32 ` [PATCH 02/12 v3] ftrace: dynamic ftrace process only text section Steven Rostedt
2008-10-23 13:32 ` [PATCH 03/12 v3] ftrace: return error on failed modified text Steven Rostedt
2008-10-23 13:33 ` [PATCH 04/12 v3] ftrace: comment arch ftrace code Steven Rostedt
2008-10-23 13:33 ` [PATCH 05/12 v3] ftrace: use probe_kernel Steven Rostedt
2008-10-23 13:33 ` [PATCH 06/12 v3] ftrace: only have ftrace_kill atomic Steven Rostedt
2008-10-23 13:33 ` [PATCH 07/12 v3] ftrace: add ftrace warn on to disable ftrace Steven Rostedt
2008-10-23 13:33 ` [PATCH 08/12 v3] ftrace: disable dynamic ftrace for all archs that use daemon Steven Rostedt
2008-10-23 13:33 ` [PATCH 09/12 v3] ftrace: remove daemon Steven Rostedt
2008-10-23 13:33 ` [PATCH 10/12 v3] ftrace: remove mcount set Steven Rostedt
2008-10-23 13:33 ` [PATCH 11/12 v3] ftrace: remove ftrace hash Steven Rostedt
2008-10-23 13:33 ` [PATCH 12/12 v3] ftrace: remove notrace from arch ftrace file Steven Rostedt
2008-10-23 14:07 ` [PATCH 00/12 v3] ftrace: clean ups and fixes Ingo Molnar

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=20081023133256.926296694@goodmis.org \
    --to=rostedt@goodmis.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=sagar.abhishek@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=wenji.huang@oracle.com \
    /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