linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH v3 0/6] tracing: export event trace and trace_marker
@ 2020-08-11  3:57 Tingwei Zhang
  2020-08-11  3:57 ` [PATCH v3 1/6] stm class: ftrace: change dependency to TRACING Tingwei Zhang
                   ` (6 more replies)
  0 siblings, 7 replies; 12+ messages in thread
From: Tingwei Zhang @ 2020-08-11  3:57 UTC (permalink / raw)
  To: Steven Rostedt, Ingo Molnar, Mathieu Poirier, Suzuki K Poulose
  Cc: Tingwei Zhang, tsoni, Sai Prakash Ranjan, Mao Jinlong,
	linux-kernel, coresight

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


^ permalink raw reply	[flat|nested] 12+ messages in thread
* [PATCH v3 0/6] tracing: export event trace and trace_marker
@ 2020-09-03  0:17 Tingwei Zhang
  2020-09-03  0:17 ` [PATCH v3 2/6] tracing: add flag to control different traces Tingwei Zhang
  0 siblings, 1 reply; 12+ messages in thread
From: Tingwei Zhang @ 2020-09-03  0:17 UTC (permalink / raw)
  To: Steven Rostedt, Ingo Molnar, Alexander Shishkin, Maxime Coquelin,
	Alexandre Torgue
  Cc: Tingwei Zhang, Mathieu Poirier, Suzuki K Poulose, tsoni,
	Sai Prakash Ranjan, Mao Jinlong, linux-kernel, linux-stm32,
	linux-arm-kernel

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


^ permalink raw reply	[flat|nested] 12+ messages in thread
* [PATCH v3 0/6] tracing: export event trace and trace_marker
@ 2020-08-13  1:45 Tingwei Zhang
  2020-08-13  1:45 ` [PATCH v3 2/6] tracing: add flag to control different traces Tingwei Zhang
  0 siblings, 1 reply; 12+ messages in thread
From: Tingwei Zhang @ 2020-08-13  1:45 UTC (permalink / raw)
  To: Steven Rostedt, Ingo Molnar, Mathieu Poirier, Suzuki K Poulose,
	Alexander Shishkin
  Cc: Tingwei Zhang, tsoni, Sai Prakash Ranjan, Mao Jinlong,
	linux-kernel, coresight

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


^ permalink raw reply	[flat|nested] 12+ messages in thread
* [PATCH v3 0/6] tracing: export event trace and trace_marker
@ 2020-07-28  1:33 Tingwei Zhang
  2020-07-28  1:33 ` [PATCH v3 2/6] tracing: add flag to control different traces Tingwei Zhang
  0 siblings, 1 reply; 12+ messages in thread
From: Tingwei Zhang @ 2020-07-28  1:33 UTC (permalink / raw)
  To: Steven Rostedt, Ingo Molnar
  Cc: Tingwei Zhang, tsoni, Sai Prakash Ranjan, Mao Jinlong, linux-kernel

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


^ permalink raw reply	[flat|nested] 12+ messages in thread

end of thread, other threads:[~2020-09-03  0:17 UTC | newest]

Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-08-11  3:57 [PATCH v3 0/6] tracing: export event trace and trace_marker Tingwei Zhang
2020-08-11  3:57 ` [PATCH v3 1/6] stm class: ftrace: change dependency to TRACING Tingwei Zhang
2020-08-11  3:57 ` [PATCH v3 2/6] tracing: add flag to control different traces Tingwei Zhang
2020-08-11  3:57 ` [PATCH v3 3/6] tracing: add trace_export support for event trace Tingwei Zhang
2020-08-11  3:57 ` [PATCH v3 4/6] tracing: add trace_export support for trace_marker Tingwei Zhang
2020-08-11  3:57 ` [PATCH v3 5/6] stm class: ftrace: enable supported trace export flag Tingwei Zhang
2020-08-11  3:57 ` [PATCH v3 6/6] stm class: ftrace: use different channel accroding to CPU Tingwei Zhang
2020-08-12 16:49 ` [PATCH v3 0/6] tracing: export event trace and trace_marker Mathieu Poirier
2020-08-13  1:47   ` Tingwei Zhang
  -- strict thread matches above, loose matches on Subject: below --
2020-09-03  0:17 Tingwei Zhang
2020-09-03  0:17 ` [PATCH v3 2/6] tracing: add flag to control different traces Tingwei Zhang
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 2/6] tracing: add flag to control different traces Tingwei Zhang
2020-07-28  1:33 [PATCH v3 0/6] tracing: export event trace and trace_marker Tingwei Zhang
2020-07-28  1:33 ` [PATCH v3 2/6] tracing: add flag to control different traces Tingwei Zhang

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).