From: Namhyung Kim <namhyung@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Namhyung Kim <namhyung.kim@lge.com>
Subject: [PATCHSET 0/4] ftrace: Add support to set_graph_notrace filter (v2)
Date: Mon, 14 Oct 2013 17:24:22 +0900 [thread overview]
Message-ID: <1381739066-7531-1-git-send-email-namhyung@kernel.org> (raw)
Hi Steve,
I broke the patch into pieces so that it can address what you said.
The patch 1 and 2 are cleanup and preparation you mentioned. Patch 3
is an one more cleanup I found during the work. Patch 4 is core of
this patchset and main diferrence to prior version is added comments.
This is based on the current linux-trace/for-next.
I also put this on 'ftrace/nograph-v2' branch in my tree
git://git.kernel.org/pub/scm/linux/kernel/git/namhyung/linux-perf.git
Any comments are welcome, thanks.
Namhyung
Namhyung Kim (4):
ftrace: Get rid of ftrace_graph_filter_enabled
ftrace: Introduce struct ftrace_graph_data
ftrace: Narrow down the protected area of graph_lock
ftrace: Add set_graph_notrace filter
include/linux/ftrace.h | 1 +
kernel/trace/ftrace.c | 140 ++++++++++++++++++++++++++---------
kernel/trace/trace.h | 25 ++++++-
kernel/trace/trace_functions_graph.c | 56 +++++++++++++-
4 files changed, 181 insertions(+), 41 deletions(-)
--
1.7.11.7
next reply other threads:[~2013-10-14 8:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-14 8:24 Namhyung Kim [this message]
2013-10-14 8:24 ` [PATCH 1/4] ftrace: Get rid of ftrace_graph_filter_enabled Namhyung Kim
2013-10-14 8:24 ` [PATCH 2/4] ftrace: Introduce struct ftrace_graph_data Namhyung Kim
2013-10-14 8:24 ` [PATCH 3/4] ftrace: Narrow down the protected area of graph_lock Namhyung Kim
2013-10-14 8:24 ` [PATCH 4/4] ftrace: Add set_graph_notrace filter Namhyung Kim
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=1381739066-7531-1-git-send-email-namhyung@kernel.org \
--to=namhyung@kernel.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung.kim@lge.com \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®