From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Frederic Weisbecker <fweisbec@gmail.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: [RFC][PATCH 0/4 v4] ftrace/kprobes: Setting up ftrace for kprobes
Date: Wed, 11 Jul 2012 15:50:48 -0400 [thread overview]
Message-ID: <20120711195048.885039013@goodmis.org> (raw)
I'm only posting patches that changed from v3. Those changes include:
Saving the flags after MCOUNT_RESTORE_FRAME (suggested by Masami)
I decided to restore flags from the pt_regs, such that a kprobe
could change the flags register.
I added the offset fix for function parent pointer (pointed out by
Alexander van Heukelum).
I fixed the i386 version of "save regs" to restore flags correctly
(as pointed out by Masami Hiramatsu).
I also added two new patches.
1) I removed the double check to function_trace_stop variable that
the function graph tracer was doing (it tested it in the function
tracer trampoline, and again in the function graph trampoline).
2) I added internal recursion protection, that I found kprobes was
triggering. This was long overdue anyway.
Masami,
Could you give your reviewed by tags for the first two patches, at least.
Thanks,
-- Steve
Steven Rostedt (4):
ftrace/x86: Add separate function to save regs
ftrace/x86: Add save_regs for i386 function calls
ftrace/x86: Remove function_trace_stop check from graph caller
ftrace/x86_64: Add recursion protection inside mcount caller
----
arch/x86/include/asm/ftrace.h | 47 +++++++++-------
arch/x86/kernel/entry_32.S | 93 ++++++++++++++++++++++++++++--
arch/x86/kernel/entry_64.S | 125 ++++++++++++++++++++++++++++++++++++-----
arch/x86/kernel/ftrace.c | 80 ++++++++++++++++++++++++--
include/linux/ftrace.h | 109 ++++++++++++++++++++++++++++++++---
kernel/trace/ftrace.c | 91 +++++++++++++++++++++++++++---
6 files changed, 485 insertions(+), 60 deletions(-)
next reply other threads:[~2012-07-11 19:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 19:50 Steven Rostedt [this message]
2012-07-11 19:50 ` [RFC][PATCH 1/4 v4] ftrace/x86: Add separate function to save regs Steven Rostedt
2012-07-12 12:12 ` Masami Hiramatsu
2012-07-11 19:50 ` [RFC][PATCH 2/4 v4] ftrace/x86: Add save_regs for i386 function calls Steven Rostedt
2012-07-12 12:39 ` Masami Hiramatsu
2012-07-12 15:53 ` Steven Rostedt
2012-07-13 18:47 ` Steven Rostedt
2012-07-17 2:08 ` Masami Hiramatsu
2012-07-17 3:05 ` Steven Rostedt
2012-07-17 3:13 ` Masami Hiramatsu
2012-07-18 15:59 ` Steven Rostedt
2012-07-19 2:20 ` Masami Hiramatsu
2012-07-19 12:52 ` Steven Rostedt
2012-07-19 12:58 ` Steven Rostedt
2012-07-19 22:53 ` H. Peter Anvin
2012-07-19 23:04 ` Steven Rostedt
2012-07-19 23:07 ` H. Peter Anvin
2012-07-20 1:27 ` Steven Rostedt
2012-07-19 18:24 ` Steven Rostedt
2012-08-21 15:03 ` [tip:perf/core] ftrace/x86_32: Simplify parameter setup for ftrace_regs_caller tip-bot for Uros Bizjak
2012-07-11 19:50 ` [RFC][PATCH 3/4 v4] ftrace/x86: Remove function_trace_stop check from graph caller Steven Rostedt
2012-08-21 15:04 ` [tip:perf/core] " tip-bot for Steven Rostedt
2012-07-11 19:50 ` [RFC][PATCH 4/4 v4] ftrace/x86_64: Add recursion protection inside mcount caller 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=20120711195048.885039013@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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