From: Tingwei Zhang <tingweiz@codeaurora.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Tingwei Zhang <tingwei@codeaurora.org>,
Ingo Molnar <mingo@redhat.com>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
tsoni@codeaurora.org,
Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>,
Mao Jinlong <jinlmao@codeaurora.org>,
linux-kernel@vger.kernel.org, coresight@lists.linaro.org
Subject: Re: [PATCH v3 0/6] tracing: export event trace and trace_marker
Date: Tue, 15 Sep 2020 07:24:48 +0800 [thread overview]
Message-ID: <20200914232448.GA20431@codeaurora.org> (raw)
In-Reply-To: <20200914184309.7a9de53a@gandalf.local.home>
On Tue, Sep 15, 2020 at 06:43:09AM +0800, Steven Rostedt wrote:
> On Wed, 2 Sep 2020 07:28:39 +0800
> Tingwei Zhang <tingweiz@codeaurora.org> wrote:
>
> > Hi Alexander,
> >
> > May I know your comments for this patch set?
>
> I ran your patch set against get_maintainers.pl and it came up with this:
>
> Alexander Shishkin <alexander.shishkin@linux.intel.com> (maintainer:SYSTEM
> TRACE MODULE CLASS)
> Maxime Coquelin <mcoquelin.stm32@gmail.com> (maintainer:ARM/STM32
> ARCHITECTURE)
> Alexandre Torgue <alexandre.torgue@st.com> (maintainer:ARM/STM32
> ARCHITECTURE)
> Steven Rostedt <rostedt@goodmis.org> (maintainer:TRACING)
> Ingo Molnar <mingo@redhat.com> (maintainer:TRACING)
> linux-stm32@st-md-mailman.stormreply.com (moderated list:ARM/STM32
> ARCHITECTURE)
> linux-arm-kernel@lists.infradead.org (moderated list:ARM/STM32
> ARCHITECTURE)
> linux-kernel@vger.kernel.org (open list)
>
> I would use that to know who to send to.
>
> You have Alexander, myself, Ingo and LKML, but you should add the others
> in
> that list for this series, and then it may get noticed. Please use
> get_maintainers.pl for future patches if you don't know who to send them
> to.
>
> -- Steve
>
Thanks a lot for the detail instructions, Steve. I noticed that after
senting previous mail to Alexander.
I sent the patchset to maintainers and mail list as you mentioned in
https://patchwork.kernel.org/cover/11752107/.
Thanks,
Tingwei
> >
> > Thanks,
> > Tingwei
> >
> > On Thu, Aug 13, 2020 at 09:45:46AM +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
> > >
>
next prev parent reply other threads:[~2020-09-14 23:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-13 1:45 [PATCH v3 0/6] tracing: export event trace and trace_marker Tingwei Zhang
2020-08-13 1:45 ` [PATCH v3 1/6] stm class: ftrace: change dependency to TRACING Tingwei Zhang
2020-08-13 1:45 ` [PATCH v3 2/6] tracing: add flag to control different traces Tingwei Zhang
2020-08-13 1:45 ` [PATCH v3 3/6] tracing: add trace_export support for event trace Tingwei Zhang
2020-08-13 1:45 ` [PATCH v3 4/6] tracing: add trace_export support for trace_marker Tingwei Zhang
2020-08-13 1:45 ` [PATCH v3 5/6] stm class: ftrace: enable supported trace export flag Tingwei Zhang
2020-08-13 1:45 ` [PATCH v3 6/6] stm class: ftrace: use different channel accroding to CPU Tingwei Zhang
2020-09-01 6:37 ` [PATCH v3 0/6] tracing: export event trace and trace_marker Tingwei Zhang
2020-09-01 17:05 ` Mathieu Poirier
2020-09-01 23:25 ` Tingwei Zhang
2020-09-01 23:28 ` Tingwei Zhang
2020-09-14 22:43 ` Steven Rostedt
2020-09-14 23:24 ` Tingwei Zhang [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-09-03 0:17 Tingwei Zhang
2020-09-03 0:17 ` Tingwei Zhang
2020-09-14 23:27 ` Tingwei Zhang
2020-09-14 23:27 ` Tingwei Zhang
2020-09-18 14:26 ` Alexander Shishkin
2020-09-18 14:26 ` Alexander Shishkin
2020-08-11 3:57 Tingwei Zhang
2020-08-12 16:49 ` Mathieu Poirier
2020-08-13 1:47 ` Tingwei Zhang
2020-07-28 1:33 Tingwei Zhang
2020-08-11 3:04 ` Tingwei Zhang
2020-08-11 3:19 ` Steven Rostedt
[not found] ` <20200811034946.GA9338@codeaurora.org>
[not found] ` <20200811000333.5d24b16f@oasis.local.home>
2020-08-11 6:45 ` 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=20200914232448.GA20431@codeaurora.org \
--to=tingweiz@codeaurora.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=coresight@lists.linaro.org \
--cc=jinlmao@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--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 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.