From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [for-next][PATCH 0/5] tracing: Better output when ftrace_bug() is hit
Date: Wed, 25 Nov 2015 21:19:03 -0500 [thread overview]
Message-ID: <20151126021903.416197072@goodmis.org> (raw)
Better output in ftrace_bug() for debugging when ftrace fails to modify
a location. Also, removed module modifications that were left over from
debugging before (rebased).
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next
Head SHA1: 39daa7b9e89512f234b7fb5d55812a78318251fc
Steven Rostedt (Red Hat) (4):
ring-buffer: Process commits whenever moving to a new page.
ftrace: Add new type to distinguish what kind of ftrace_bug()
ftrace: Add variable ftrace_expected for archs to show expected code
ftrace: Show all tramps registered to a record on ftrace_bug()
Tom Zanussi (1):
tracing: Update cond flag when enabling or disabling a trigger
----
arch/x86/kernel/ftrace.c | 9 ++++
include/linux/ftrace.h | 15 ++++++
kernel/trace/ftrace.c | 92 ++++++++++++++++++++++++++++++++-----
kernel/trace/ring_buffer.c | 7 +++
kernel/trace/trace_events_trigger.c | 10 ++--
5 files changed, 117 insertions(+), 16 deletions(-)
next reply other threads:[~2015-11-26 2:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 2:19 Steven Rostedt [this message]
2015-11-26 2:19 ` [for-next][PATCH 1/5] ring-buffer: Process commits whenever moving to a new page Steven Rostedt
2015-11-26 2:19 ` [for-next][PATCH 2/5] tracing: Update cond flag when enabling or disabling a trigger Steven Rostedt
2015-11-26 2:19 ` [for-next][PATCH 3/5] ftrace: Add new type to distinguish what kind of ftrace_bug() Steven Rostedt
2015-11-26 2:19 ` [for-next][PATCH 4/5] ftrace: Add variable ftrace_expected for archs to show expected code Steven Rostedt
2015-11-26 2:19 ` [for-next][PATCH 5/5] ftrace: Show all tramps registered to a record on ftrace_bug() 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=20151126021903.416197072@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--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