All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Todd Brandt <todd.e.brandt@linux.intel.com>
Subject: [RFC][PATCH 0/4] tracing: Allow function tracing to start earlier in boot up
Date: Tue, 07 Mar 2017 16:28:33 -0500	[thread overview]
Message-ID: <20170307212833.964734229@goodmis.org> (raw)

I've had people ask about moving tracing up further in the boot process.
This patch series looks at function tracing only. It allows for tracing
(and function filtering) to be moved right after memory is initialized.
To have it happen before memory initialization would require a bit more
work with allocating the ring buffer. But this is a start.

I placed a hook into free_reserved_area() which is used by all archs
to free the init memory. Having it pass the range being freed to ftrace
lets ftrace clean up any function that is registered such that it doesn't
try to modify code that no longer exists. 


Steven Rostedt (VMware) (4):
      tracing: Split tracing initialization into two for early initialization
      ftrace: Move ftrace_init() to right after memory initialization
      ftrace: Have function tracing start in early boot up
      ftrace: Allow for function tracing to record init functions on boot up

----
 include/linux/ftrace.h         |  5 +++++
 include/linux/init.h           |  4 +++-
 init/main.c                    |  9 ++++++---
 kernel/trace/ftrace.c          | 44 ++++++++++++++++++++++++++++++++++++++++++
 kernel/trace/trace.c           |  9 ++++++++-
 kernel/trace/trace.h           |  2 ++
 kernel/trace/trace_functions.c |  3 +--
 mm/page_alloc.c                |  4 ++++
 scripts/recordmcount.c         |  1 +
 scripts/recordmcount.pl        |  1 +
 10 files changed, 75 insertions(+), 7 deletions(-)

             reply	other threads:[~2017-03-07 21:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-07 21:28 Steven Rostedt [this message]
2017-03-07 21:28 ` [RFC][PATCH 1/4] tracing: Split tracing initialization into two for early initialization Steven Rostedt
2017-03-07 21:28 ` [RFC][PATCH 2/4] ftrace: Move ftrace_init() to right after memory initialization Steven Rostedt
2017-03-07 21:28 ` [RFC][PATCH 3/4] ftrace: Have function tracing start in early boot up Steven Rostedt
2017-03-07 21:28 ` [RFC][PATCH 4/4] ftrace: Allow for function tracing to record init functions on " Steven Rostedt
2017-03-07 21:28   ` Steven Rostedt
2017-03-08 20:07   ` Steven Rostedt
2017-03-08 20:07     ` Steven Rostedt
2017-03-08 19:15 ` [RFC][PATCH 0/4] tracing: Allow function tracing to start earlier in " Todd Brandt
2017-03-08 19:32   ` Todd Brandt
2017-03-08 19:36     ` 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=20170307212833.964734229@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=todd.e.brandt@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.