linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: zhang.chunyan@linaro.org (Chunyan Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 3/4] trace: Duplicate the output of the function trace logs to STM
Date: Wed,  1 Jun 2016 19:18:58 +0800	[thread overview]
Message-ID: <1464779939-24986-4-git-send-email-zhang.chunyan@linaro.org> (raw)
In-Reply-To: <1464779939-24986-1-git-send-email-zhang.chunyan@linaro.org>

This patch adds an output from Ftrace to STM.  That being said,
Function trace messages would also be duplicated to STM buffer when
being stored into ring buffer.

Signed-off-by: Chunyan Zhang <zhang.chunyan@linaro.org>
---
 kernel/trace/trace.c | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
index 8a4bd6b..d613053 100644
--- a/kernel/trace/trace.c
+++ b/kernel/trace/trace.c
@@ -44,6 +44,7 @@
 
 #include "trace.h"
 #include "trace_output.h"
+#include "trace_output_stm.h"
 
 /*
  * On boot up, the ring buffer is set to the minimum size, so that
@@ -1884,8 +1885,10 @@ trace_function(struct trace_array *tr,
 	entry->ip			= ip;
 	entry->parent_ip		= parent_ip;
 
-	if (!call_filter_check_discard(call, entry, buffer, event))
+	if (!call_filter_check_discard(call, entry, buffer, event)) {
 		__buffer_unlock_commit(buffer, event);
+		ftrace_stm_func(ip, parent_ip);
+	}
 }
 
 #ifdef CONFIG_STACKTRACE
-- 
1.9.1

  parent reply	other threads:[~2016-06-01 11:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-01 11:18 [RFC PATCH 0/4] Integration of function trace with System Trace IP blocks Chunyan Zhang
2016-06-01 11:18 ` [RFC PATCH 1/4] STM Ftrace: Adding generic buffer interface driver Chunyan Zhang
2016-06-07 10:25   ` Alexander Shishkin
2016-06-08 11:01     ` Chunyan Zhang
2016-06-08 12:13       ` Alexander Shishkin
2016-06-13  7:00         ` Chunyan Zhang
2016-06-01 11:18 ` [RFC PATCH 2/4] trace: Introduce an output interface from ftrace to STM Chunyan Zhang
2016-06-07 10:04   ` Alexander Shishkin
2016-06-08 11:02     ` Chunyan Zhang
2016-06-09  8:54       ` Alexander Shishkin
2016-06-20  9:22     ` Chunyan Zhang
2016-06-01 11:18 ` Chunyan Zhang [this message]
2016-06-07 10:00   ` [RFC PATCH 3/4] trace: Duplicate the output of the function trace logs " Alexander Shishkin
2016-06-08 11:02     ` Chunyan Zhang
2016-06-01 11:18 ` [RFC PATCH 4/4] stm: Mark the functions of writing buffer with notrace Chunyan Zhang
2016-06-17 16:26   ` Steven Rostedt
2016-06-07 10:50 ` [RFC PATCH 0/4] Integration of function trace with System Trace IP blocks Alexander Shishkin
2016-06-08 11:01   ` Chunyan Zhang

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=1464779939-24986-4-git-send-email-zhang.chunyan@linaro.org \
    --to=zhang.chunyan@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).