From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [for-next-3.11][PATCH 00/12] tracing: Cleanups and fixes
Date: Fri, 19 Jul 2013 10:12:24 -0400 [thread overview]
Message-ID: <20130719141224.703522101@goodmis.org> (raw)
These are mostly cleanups and some minor fixes. Still working on
fixing a theoretical race with trace events.
-- Steve
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next
Head SHA1: cd458ba9d5a5592d37b5145e560071e91ea762ac
Alexander Z Lam (2):
tracing: Fix error handling to ensure instances can always be removed
tracing: Miscellaneous fixes for trace_array ref counting
Masami Hiramatsu (1):
tracing/kprobe: Wait for disabling all running kprobe handlers
Oleg Nesterov (5):
tracing/function: Avoid perf_trace_buf_*() if event_function.perf_events is empty
tracing/syscall: Avoid perf_trace_buf_*() if sys_data->perf_events is empty
tracing/perf: Move the PERF_MAX_TRACE_SIZE check into perf_trace_buf_prepare()
tracing: Simplify the iteration logic in f_start/f_next
tracing: Do not (ab)use trace_seq in event_id_read()
Steven Rostedt (Red Hat) (1):
tracing: Add ref_data to function and fgraph tracer structs
zhangwei(Jovi) (3):
tracing: Use correct config guard CONFIG_STACK_TRACER
tracing: Use trace_seq_puts()/trace_seq_putc() where possible
tracing: Typo fix on ring buffer comments
----
include/trace/ftrace.h | 4 --
kernel/trace/ring_buffer.c | 26 ++++-----
kernel/trace/trace.c | 32 +++++++----
kernel/trace/trace.h | 9 ++++
kernel/trace/trace_event_perf.c | 10 +++-
kernel/trace/trace_events.c | 98 ++++++++++++++++------------------
kernel/trace/trace_events_filter.c | 4 +-
kernel/trace/trace_functions.c | 2 +-
kernel/trace/trace_functions_graph.c | 54 +++++++++----------
kernel/trace/trace_kprobe.c | 29 +++++-----
kernel/trace/trace_mmiotrace.c | 8 +--
kernel/trace/trace_output.c | 14 ++---
kernel/trace/trace_syscalls.c | 26 ++++-----
kernel/trace/trace_uprobe.c | 2 -
14 files changed, 166 insertions(+), 152 deletions(-)
next reply other threads:[~2013-07-19 14:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 14:12 Steven Rostedt [this message]
2013-07-19 14:12 ` [for-next-3.11][PATCH 01/12] tracing: Use correct config guard CONFIG_STACK_TRACER Steven Rostedt
2013-07-19 14:12 ` [for-next-3.11][PATCH 02/12] tracing: Use trace_seq_puts()/trace_seq_putc() where possible Steven Rostedt
2013-07-19 14:12 ` [for-next-3.11][PATCH 03/12] tracing: Typo fix on ring buffer comments Steven Rostedt
2013-07-19 14:12 ` [for-next-3.11][PATCH 04/12] tracing/function: Avoid perf_trace_buf_*() if event_function.perf_events is empty Steven Rostedt
2013-07-19 14:12 ` [for-next-3.11][PATCH 05/12] tracing/syscall: Avoid perf_trace_buf_*() if sys_data->perf_events " Steven Rostedt
2013-07-19 14:12 ` [for-next-3.11][PATCH 06/12] tracing/perf: Move the PERF_MAX_TRACE_SIZE check into perf_trace_buf_prepare() Steven Rostedt
2013-07-19 14:12 ` [for-next-3.11][PATCH 07/12] tracing/kprobe: Wait for disabling all running kprobe handlers Steven Rostedt
2013-07-19 14:12 ` [for-next-3.11][PATCH 08/12] tracing: Fix error handling to ensure instances can always be removed Steven Rostedt
2013-07-19 14:12 ` [for-next-3.11][PATCH 09/12] tracing: Miscellaneous fixes for trace_array ref counting Steven Rostedt
2013-07-19 14:12 ` [for-next-3.11][PATCH 10/12] tracing: Add ref_data to function and fgraph tracer structs Steven Rostedt
2013-07-19 14:12 ` [for-next-3.11][PATCH 11/12] tracing: Simplify the iteration logic in f_start/f_next Steven Rostedt
2013-07-19 14:12 ` [for-next-3.11][PATCH 12/12] tracing: Do not (ab)use trace_seq in event_id_read() 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=20130719141224.703522101@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
/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