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] ftrace: More stuff for 3.19
Date: Tue, 25 Nov 2014 07:13:55 -0500 [thread overview]
Message-ID: <20141125121355.225538266@goodmis.org> (raw)
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next
Head SHA1: 62a207d748dd9224140a634786b274fdb6ece0b9
Masami Hiramatsu (3):
kprobes/ftrace: Recover original IP if pre_handler doesn't change it
ftrace, kprobes: Support IPMODIFY flag to find IP modify conflict
kprobes: Add IPMODIFY flag to kprobe_ftrace_ops
Steven Rostedt (Red Hat) (2):
tracing/trivial: Fix typos and make an int into a bool
ftrace/x86: Have static function tracing always test for function graph
----
Documentation/trace/ftrace.txt | 5 ++
arch/x86/kernel/kprobes/ftrace.c | 9 ++-
arch/x86/kernel/mcount_64.S | 3 +-
include/linux/ftrace.h | 16 ++++-
kernel/kprobes.c | 2 +-
kernel/trace/ftrace.c | 144 ++++++++++++++++++++++++++++++++++++++-
kernel/trace/trace_functions.c | 6 +-
7 files changed, 172 insertions(+), 13 deletions(-)
next reply other threads:[~2014-11-25 12:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-25 12:13 Steven Rostedt [this message]
2014-11-25 12:13 ` [for-next][PATCH 1/5] tracing/trivial: Fix typos and make an int into a bool Steven Rostedt
2014-11-25 12:13 ` [for-next][PATCH 2/5] kprobes/ftrace: Recover original IP if pre_handler doesnt change it Steven Rostedt
2014-11-25 12:13 ` [for-next][PATCH 3/5] ftrace, kprobes: Support IPMODIFY flag to find IP modify conflict Steven Rostedt
2014-11-25 12:13 ` [for-next][PATCH 4/5] kprobes: Add IPMODIFY flag to kprobe_ftrace_ops Steven Rostedt
2014-11-25 12:14 ` [for-next][PATCH 5/5] ftrace/x86: Have static function tracing always test for function graph 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=20141125121355.225538266@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
Powered by JetHome