From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: [PATCH 00/16] [GIT PULL] tracing: fixes/cleanups, no stop-machine, update stack tracer
Date: Wed, 21 Dec 2011 07:36:24 -0500 [thread overview]
Message-ID: <20111221123624.193898256@goodmis.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2494 bytes --]
Ingo,
This patch set contains a few things.
1) various fixes and cleanups, one is even marked as stable, but its
a minor bug fix that probably is not worth pushing to mainline this
late in the -rc.
2) The infrastructure to use ftrace function tracing without stop_machine.
Although x86 doesn't have the iret code finished to do this yet,
other archs like PPC can. This will also test out the code better.
Note, it's just a single patch left that converts x86 to use this code.
3) Moving the stack tracer to its own function list. As Jiri is
working on having perf do function tracing, he found a few bugs
that were hard to find without another user outside the global users.
It makes sense to have the stack tracer separate from the function
tracer anyway, and it gives a good test bed for perf and function
tracing as well.
-- Steve
Please pull the latest tip/perf/core tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
tip/perf/core
Head SHA1: 38b78eb855409a05f9d370228bec1955e6878e08
Jiri Olsa (1):
ftrace: Fix unregister ftrace_ops accounting
Steven Rostedt (14):
ftrace: Do not function trace inlined functions
ftrace: Allow archs to modify code without stop machine
ftrace: Remove usage of "freed" records
ftrace: Allocate the mcount record pages as groups
ftrace: Replace record newlist with record page list
ftrace: Sort the mcount records on each page
ftrace: Use bsearch to find record ip
ftrace: Fix ftrace hash record update with notrace
ftrace: Create ftrace_hash_empty() helper routine
ftrace: Allow other users of function tracing to use the output listing
ftrace: Decouple hash items from showing filtered functions
tracing: Have stack_tracer use a separate list of functions
ftrace: Allow access to the boot time function enabling
tracing: Have stack tracing set filtered functions at boot
Tejun Heo (1):
tracing: Factorize filter creation
----
Documentation/kernel-parameters.txt | 8 +
include/linux/compiler-gcc.h | 5 +
include/linux/ftrace.h | 76 ++++-
kernel/trace/ftrace.c | 715 +++++++++++++++++++++++++----------
kernel/trace/trace_events_filter.c | 283 +++++++-------
kernel/trace/trace_stack.c | 30 ++-
6 files changed, 767 insertions(+), 350 deletions(-)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2011-12-21 12:38 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 12:36 Steven Rostedt [this message]
2011-12-21 12:36 ` [PATCH 01/16] ftrace: Fix unregister ftrace_ops accounting Steven Rostedt
2011-12-21 12:36 ` [PATCH 02/16] ftrace: Do not function trace inlined functions Steven Rostedt
2011-12-21 12:36 ` [PATCH 03/16] ftrace: Allow archs to modify code without stop machine Steven Rostedt
2011-12-21 12:36 ` [PATCH 04/16] ftrace: Remove usage of "freed" records Steven Rostedt
2011-12-21 12:36 ` [PATCH 05/16] ftrace: Allocate the mcount record pages as groups Steven Rostedt
2011-12-21 12:36 ` [PATCH 06/16] ftrace: Replace record newlist with record page list Steven Rostedt
2011-12-21 12:36 ` [PATCH 07/16] ftrace: Sort the mcount records on each page Steven Rostedt
2011-12-21 12:36 ` [PATCH 08/16] ftrace: Use bsearch to find record ip Steven Rostedt
2011-12-21 12:36 ` [PATCH 09/16] ftrace: Fix ftrace hash record update with notrace Steven Rostedt
2011-12-21 12:36 ` [PATCH 10/16] ftrace: Create ftrace_hash_empty() helper routine Steven Rostedt
2011-12-21 12:36 ` [PATCH 11/16] ftrace: Allow other users of function tracing to use the output listing Steven Rostedt
2011-12-21 12:36 ` [PATCH 12/16] ftrace: Decouple hash items from showing filtered functions Steven Rostedt
2011-12-21 12:36 ` [PATCH 13/16] tracing: Have stack_tracer use a separate list of functions Steven Rostedt
2011-12-21 12:36 ` [PATCH 14/16] ftrace: Allow access to the boot time function enabling Steven Rostedt
2011-12-21 12:36 ` [PATCH 15/16] tracing: Have stack tracing set filtered functions at boot Steven Rostedt
2011-12-21 12:36 ` [PATCH 16/16] tracing: Factorize filter creation Steven Rostedt
2012-01-01 18:09 ` [PATCH 00/16] [GIT PULL] tracing: fixes/cleanups, no stop-machine, update stack tracer Ingo Molnar
2012-01-02 10:58 ` Ingo Molnar
2012-01-02 13:48 ` Ingo Molnar
2012-01-02 15:10 ` Ingo Molnar
2012-01-04 0:02 ` Steven Rostedt
2012-01-04 0:12 ` Steven Rostedt
2012-01-04 5:01 ` Steven Rostedt
2012-01-04 14:11 ` Ingo Molnar
2012-01-04 17:05 ` Steven Rostedt
2012-01-04 18:39 ` Ingo Molnar
2012-01-05 9:19 ` Ingo Molnar
2012-01-05 11:46 ` Steven Rostedt
2012-01-05 12:16 ` Steven Rostedt
2012-01-06 4:58 ` Steven Rostedt
2012-01-06 8:51 ` Ingo Molnar
2012-01-06 12:10 ` Steven Rostedt
2012-01-06 15:29 ` Steven Rostedt
2012-01-07 12:20 ` Ingo Molnar
2012-01-07 12:25 ` Ingo Molnar
2012-01-07 22:32 ` Steven Rostedt
2012-01-08 11:38 ` Ingo Molnar
2012-01-02 19:33 ` Steven Rostedt
2012-01-06 5:04 ` 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=20111221123624.193898256@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
Powered by JetHome