From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
"zhangwei(Jovi)" <jovi.zhangwei@huawei.com>
Subject: [for-next][PATCH 0/9] tracing: ring-buffer selftest, cleanups, ftrace_dump() fix and document
Date: Fri, 15 Mar 2013 23:24:12 -0400 [thread overview]
Message-ID: <20130316032412.416651612@goodmis.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2291 bytes --]
One more linux-next patch series.
The first patch is a ring buffer boot time selftest. A bug in my development
code looked like the ring buffer was dropping events, and I wrote a test
to make sure that wasn't the case. The bug ended up being a stupid
mistake in my development code, but the ring buffer test seemed like a
good idea to include in the kernel as an option.
Next is a series of clean ups by Jovi.
Jovi also pointed out issues with ftrace_dump(). It's been on my todo
list to clean up ftrace_dump() for a long time, and finally decided
to do so. It wasn't hard and was quick to do. There was a long standing
bug where an NMI triggering a dump while another dump was happening
could cause a deadlock. I marked that patch for stable, but since its
really just a debugging tool and I don't recall ever hitting the deadlock
(I might have), I decided it can wait for 3.10 and I'll do the backports
when I get the "Failed to apply" messages from Greg Kroah-Hartman's
stable scripts.
Last patch brings the README file in debugfs/tracing/ up to date with
more useful information.
Enjoy!
-- Steve
Steven Rostedt (Red Hat) (3):
ring-buffer: Add ring buffer startup selftest
tracing: Fix ftrace_dump()
tracing: Update debugfs README file
zhangwei(Jovi) (6):
tracing: Use pr_warn_once instead of open coded implementation
tracing: Use TRACE_MAX_PRINT instead of constant
tracing: Move find_event_field() into trace_events.c
tracing: Convert trace_destroy_fields() to static
tracing: Fix comment about prefix in arch_syscall_match_sym_name()
tracing: Rename trace_event_mutex to trace_event_sem
----
kernel/trace/Kconfig | 23 +++
kernel/trace/ring_buffer.c | 319 ++++++++++++++++++++++++++++++++++++
kernel/trace/trace.c | 164 +++++++++++-------
kernel/trace/trace.h | 6 +-
kernel/trace/trace_events.c | 55 +++++--
kernel/trace/trace_events_filter.c | 29 +---
kernel/trace/trace_output.c | 16 +-
kernel/trace/trace_output.h | 2 +-
kernel/trace/trace_selftest.c | 9 +-
kernel/trace/trace_syscalls.c | 2 +-
10 files changed, 506 insertions(+), 119 deletions(-)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next reply other threads:[~2013-03-16 3:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-16 3:24 Steven Rostedt [this message]
2013-03-16 3:24 ` [for-next][PATCH 1/9] ring-buffer: Add ring buffer startup selftest Steven Rostedt
2013-03-16 3:24 ` [for-next][PATCH 2/9] tracing: Use pr_warn_once instead of open coded implementation Steven Rostedt
2013-03-16 3:24 ` [for-next][PATCH 3/9] tracing: Use TRACE_MAX_PRINT instead of constant Steven Rostedt
2013-03-16 3:24 ` [for-next][PATCH 4/9] tracing: Move find_event_field() into trace_events.c Steven Rostedt
2013-03-16 3:24 ` [for-next][PATCH 5/9] tracing: Convert trace_destroy_fields() to static Steven Rostedt
2013-03-16 3:24 ` [for-next][PATCH 6/9] tracing: Fix comment about prefix in arch_syscall_match_sym_name() Steven Rostedt
2013-03-16 3:24 ` [for-next][PATCH 7/9] tracing: Rename trace_event_mutex to trace_event_sem Steven Rostedt
2013-03-16 3:24 ` [for-next][PATCH 8/9] tracing: Fix ftrace_dump() Steven Rostedt
2013-03-16 3:24 ` [for-next][PATCH 9/9] tracing: Update debugfs README file Steven Rostedt
2013-03-18 8:22 ` Namhyung Kim
2013-03-18 9:03 ` Keun-O Park
2013-03-18 13:19 ` Steven Rostedt
2013-03-21 2:02 ` Steven Rostedt
2013-03-18 13:18 ` 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=20130316032412.416651612@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=jovi.zhangwei@huawei.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