From: Tingwei Zhang <tingweiz@codeaurora.org>
To: Tingwei Zhang <tingwei@codeaurora.org>
Cc: tsoni@codeaurora.org,
Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>,
Alexandre Torgue <alexandre.torgue@st.com>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Mao Jinlong <jinlmao@codeaurora.org>,
linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/6] tracing: export event trace and trace_marker
Date: Tue, 15 Sep 2020 07:27:29 +0800 [thread overview]
Message-ID: <20200914232729.GB20431@codeaurora.org> (raw)
In-Reply-To: <20200903001706.28147-1-tingwei@codeaurora.org>
Hi Alexander, Maxime, Aleandre,
May I know your comments for this patch set?
Thanks,
Tingwei
On Thu, Sep 03, 2020 at 08:17:00AM +0800, Tingwei Zhang wrote:
> 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 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 prev parent reply other threads:[~2020-09-14 23:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 0:17 [PATCH v3 0/6] tracing: export event trace and trace_marker Tingwei Zhang
2020-09-03 0:17 ` [PATCH v3 1/6] stm class: ftrace: change dependency to TRACING Tingwei Zhang
2020-09-03 0:17 ` [PATCH v3 2/6] tracing: add flag to control different traces Tingwei Zhang
2020-09-03 0:17 ` [PATCH v3 3/6] tracing: add trace_export support for event trace Tingwei Zhang
2020-09-03 0:17 ` [PATCH v3 4/6] tracing: add trace_export support for trace_marker Tingwei Zhang
2020-09-03 0:17 ` [PATCH v3 5/6] stm class: ftrace: enable supported trace export flag Tingwei Zhang
2020-09-03 0:17 ` [PATCH v3 6/6] stm class: ftrace: use different channel accroding to CPU Tingwei Zhang
2020-09-18 12:45 ` Alexander Shishkin
2020-09-23 4:39 ` Tingwei Zhang
2020-09-14 23:27 ` Tingwei Zhang [this message]
2020-09-18 14:26 ` [PATCH v3 0/6] tracing: export event trace and trace_marker Alexander Shishkin
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=20200914232729.GB20431@codeaurora.org \
--to=tingweiz@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=tingwei@codeaurora.org \
--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: 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).