From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932250AbcFGKA1 (ORCPT ); Tue, 7 Jun 2016 06:00:27 -0400 Received: from mga09.intel.com ([134.134.136.24]:54545 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754263AbcFGKA0 (ORCPT ); Tue, 7 Jun 2016 06:00:26 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.26,432,1459839600"; d="scan'208";a="823214014" From: Alexander Shishkin To: Chunyan Zhang , rostedt@goodmis.org, mathieu.poirier@linaro.org, mingo@redhat.com Cc: mike.leach@arm.com, tor@ti.com, maxime.coquelin@st.com, philippe.langlais@st.com, nicolas.guion@st.com, zhang.lyra@gmail.com, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [RFC PATCH 3/4] trace: Duplicate the output of the function trace logs to STM In-Reply-To: <1464779939-24986-4-git-send-email-zhang.chunyan@linaro.org> References: <1464779939-24986-1-git-send-email-zhang.chunyan@linaro.org> <1464779939-24986-4-git-send-email-zhang.chunyan@linaro.org> User-Agent: Notmuch/0.21 (http://notmuchmail.org) Emacs/24.5.1 (x86_64-pc-linux-gnu) Date: Tue, 07 Jun 2016 13:00:21 +0300 Message-ID: <87lh2hqpxm.fsf@ashishki-desk.ger.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Chunyan Zhang writes: > This patch adds an output from Ftrace to STM. But does it? > That being said, > Function trace messages would also be duplicated to STM buffer when > being stored into ring buffer. Not sure what you mean here. What's "STM buffer"? > > Signed-off-by: Chunyan Zhang > --- > 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); > + } So this logs instruction pointers, not the actual events. Not much is duplicated like the message suggests, but it also doesn't seem very useful. Regards, -- Alex