From: Tingwei Zhang <tingwei@codeaurora.org> To: Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@redhat.com>, Alexander Shishkin <alexander.shishkin@linux.intel.com>, Maxime Coquelin <mcoquelin.stm32@gmail.com>, Alexandre Torgue <alexandre.torgue@st.com> Cc: Tingwei Zhang <tingwei@codeaurora.org>, Mathieu Poirier <mathieu.poirier@linaro.org>, Suzuki K Poulose <suzuki.poulose@arm.com>, tsoni@codeaurora.org, Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>, Mao Jinlong <jinlmao@codeaurora.org>, linux-kernel@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, linux-arm-kernel@lists.infradead.org Subject: [PATCH v4 0/6] tracing: export event trace and trace_marker Date: Sat, 26 Sep 2020 08:59:59 +0800 [thread overview] Message-ID: <20200926010005.14689-1-tingwei@codeaurora.org> (raw) Ftrace has ability to export trace packets to other destination. Currently, only function trace can be exported. This series extends the support to event trace and trace_maker. STM is one possible destination to export ftrace. Use separate channel for each CPU to avoid mixing up packets from different CPUs together. Change from v3: Round up number of channels to power of 2. (Alex) Change from v2: Change flag definition to BIT(). (Steven) Add comment in stm_ftrace_write() to clarify it's safe to use smp_processor_id() here since preempt is disabled. (Steven) Change from v1: All changes are suggested by Steven Rostedt. User separate flag to control function trace, event trace and trace mark. Allocate channels according to num_possible_cpu() dynamically. Move ftrace_exports routines up so all ftrace can use them. Tingwei Zhang (6): stm class: ftrace: change dependency to TRACING tracing: add flag to control different traces tracing: add trace_export support for event trace tracing: add trace_export support for trace_marker stm class: ftrace: enable supported trace export flag stm class: ftrace: use different channel accroding to CPU drivers/hwtracing/stm/Kconfig | 2 +- drivers/hwtracing/stm/ftrace.c | 7 +- include/linux/trace.h | 7 + kernel/trace/trace.c | 270 ++++++++++++++++++--------------- 4 files changed, 159 insertions(+), 127 deletions(-) -- The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project
WARNING: multiple messages have this Message-ID (diff)
From: Tingwei Zhang <tingwei@codeaurora.org> To: Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@redhat.com>, Alexander Shishkin <alexander.shishkin@linux.intel.com>, Maxime Coquelin <mcoquelin.stm32@gmail.com>, Alexandre Torgue <alexandre.torgue@st.com> Cc: tsoni@codeaurora.org, Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>, Mathieu Poirier <mathieu.poirier@linaro.org>, Suzuki K Poulose <suzuki.poulose@arm.com>, Mao Jinlong <jinlmao@codeaurora.org>, linux-kernel@vger.kernel.org, Tingwei Zhang <tingwei@codeaurora.org>, linux-stm32@st-md-mailman.stormreply.com, linux-arm-kernel@lists.infradead.org Subject: [PATCH v4 0/6] tracing: export event trace and trace_marker Date: Sat, 26 Sep 2020 08:59:59 +0800 [thread overview] Message-ID: <20200926010005.14689-1-tingwei@codeaurora.org> (raw) Ftrace has ability to export trace packets to other destination. Currently, only function trace can be exported. This series extends the support to event trace and trace_maker. STM is one possible destination to export ftrace. Use separate channel for each CPU to avoid mixing up packets from different CPUs together. Change from v3: Round up number of channels to power of 2. (Alex) Change from v2: Change flag definition to BIT(). (Steven) Add comment in stm_ftrace_write() to clarify it's safe to use smp_processor_id() here since preempt is disabled. (Steven) Change from v1: All changes are suggested by Steven Rostedt. User separate flag to control function trace, event trace and trace mark. Allocate channels according to num_possible_cpu() dynamically. Move ftrace_exports routines up so all ftrace can use them. Tingwei Zhang (6): stm class: ftrace: change dependency to TRACING tracing: add flag to control different traces tracing: add trace_export support for event trace tracing: add trace_export support for trace_marker stm class: ftrace: enable supported trace export flag stm class: ftrace: use different channel accroding to CPU drivers/hwtracing/stm/Kconfig | 2 +- drivers/hwtracing/stm/ftrace.c | 7 +- include/linux/trace.h | 7 + kernel/trace/trace.c | 270 ++++++++++++++++++--------------- 4 files changed, 159 insertions(+), 127 deletions(-) -- The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-09-26 1:01 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-26 0:59 Tingwei Zhang [this message] 2020-09-26 0:59 ` [PATCH v4 0/6] tracing: export event trace and trace_marker Tingwei Zhang 2020-09-26 1:00 ` [PATCH v4 1/6] stm class: ftrace: change dependency to TRACING Tingwei Zhang 2020-09-26 1:00 ` Tingwei Zhang 2020-09-26 1:00 ` [PATCH v4 2/6] tracing: add flag to control different traces Tingwei Zhang 2020-09-26 1:00 ` Tingwei Zhang 2020-09-26 1:00 ` [PATCH v4 3/6] tracing: add trace_export support for event trace Tingwei Zhang 2020-09-26 1:00 ` Tingwei Zhang 2020-09-26 1:00 ` [PATCH v4 4/6] tracing: add trace_export support for trace_marker Tingwei Zhang 2020-09-26 1:00 ` Tingwei Zhang 2020-09-26 1:00 ` [PATCH v4 5/6] stm class: ftrace: enable supported trace export flag Tingwei Zhang 2020-09-26 1:00 ` Tingwei Zhang 2020-09-26 1:00 ` [PATCH v4 6/6] stm class: ftrace: use different channel accroding to CPU Tingwei Zhang 2020-09-26 1:00 ` Tingwei 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=20200926010005.14689-1-tingwei@codeaurora.org \ --to=tingwei@codeaurora.org \ --cc=alexander.shishkin@linux.intel.com \ --cc=alexandre.torgue@st.com \ --cc=jinlmao@codeaurora.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-stm32@st-md-mailman.stormreply.com \ --cc=mathieu.poirier@linaro.org \ --cc=mcoquelin.stm32@gmail.com \ --cc=mingo@redhat.com \ --cc=rostedt@goodmis.org \ --cc=saiprakash.ranjan@codeaurora.org \ --cc=suzuki.poulose@arm.com \ --cc=tsoni@codeaurora.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.