From: Daniel Bristot de Oliveira <bristot@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Daniel Bristot de Oliveira <bristot@kernel.org>,
Ingo Molnar <mingo@redhat.com>, Tom Zanussi <zanussi@kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Juri Lelli <juri.lelli@redhat.com>,
Clark Williams <williams@redhat.com>,
John Kacur <jkacur@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-rt-users@vger.kernel.org,
linux-trace-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH V8 0/9] tracing/osnoise: Support multiple instances (for RTLA)
Date: Fri, 29 Oct 2021 21:00:26 +0200 [thread overview]
Message-ID: <cover.1635533292.git.bristot@kernel.org> (raw)
Currently, osnoise and timerlat run only on a single instance. To reduce
this limitation, this series adds support for parallel instances of the
same tracer. That is, it is possible to run two instances of osnoise
tracer with different configurations. For example, one for the tracer
output and another for a set of tracepoints.
This patchset is the kernel dependencies for RTLA. This patchset was
being sent along with RTLA [1], but we split the kernel and
user-space patch sets.
[1] RTLA: An interface for osnoise/timerlat tracers:
https://lore.kernel.org/lkml/cover.1635284863.git.bristot@kernel.org/
Changes from v7:
- Fix check for print_stack disabled
- Fix thread/sofitrq filter when TIMERLAT ifdef is enabled
Both fixes for the patches added in the v6.
Changes from v6:
- Fix compilation problems for the case in which osnoise
enabled, but timerlat disabled (Steven)
- Remove ifdefs from inside functions (Steven)
Changes that happened while in the RTLA patchset:
- Fix comment on start_per_cpu_kthreads() (Steven)
- Fix msg log on patch 1
- Add comments about the barrier need for trace_nmi_enter/exit
- Fix RCU usage in osnoise_unregister_instance() (Steven/Paul)
- Add lockdep checks in osnoise_unregister/unregister_instance()
(Steven/Paul)
- Improve the explanation about the multi instances support (Steven)
Daniel Bristot de Oliveira (9):
tracing/osnoise: Do not follow tracing_cpumask
tracing/osnoise: Improve comments about barrier need for NMI callbacks
tracing/osnoise: Split workload start from the tracer start
tracing/osnoise: Use start/stop_per_cpu_kthreads() on
osnoise_cpus_write()
tracing/osnoise: Support a list of trace_array *tr
tracing/osnoise: Remove TIMERLAT ifdefs from inside functions
tracing/osnoise: Allow multiple instances of the same tracer
tracing/osnoise: Remove STACKTRACE ifdefs from inside functions
tracing/osnoise: Remove PREEMPT_RT ifdefs from inside functions
kernel/trace/trace_osnoise.c | 615 ++++++++++++++++++++++++-----------
1 file changed, 434 insertions(+), 181 deletions(-)
--
2.31.1
next reply other threads:[~2021-10-29 19:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 19:00 Daniel Bristot de Oliveira [this message]
2021-10-29 19:00 ` [PATCH V8 1/9] tracing/osnoise: Do not follow tracing_cpumask Daniel Bristot de Oliveira
2021-10-29 19:00 ` [PATCH V8 2/9] tracing/osnoise: Improve comments about barrier need for NMI callbacks Daniel Bristot de Oliveira
2021-10-29 19:00 ` [PATCH V8 3/9] tracing/osnoise: Split workload start from the tracer start Daniel Bristot de Oliveira
2021-10-29 19:00 ` [PATCH V8 4/9] tracing/osnoise: Use start/stop_per_cpu_kthreads() on osnoise_cpus_write() Daniel Bristot de Oliveira
2021-10-29 19:00 ` [PATCH V8 5/9] tracing/osnoise: Support a list of trace_array *tr Daniel Bristot de Oliveira
2021-10-29 19:00 ` [PATCH V8 6/9] tracing/osnoise: Remove TIMERLAT ifdefs from inside functions Daniel Bristot de Oliveira
2021-10-29 19:00 ` [PATCH V8 7/9] tracing/osnoise: Allow multiple instances of the same tracer Daniel Bristot de Oliveira
2021-10-29 19:00 ` [PATCH V8 8/9] tracing/osnoise: Remove STACKTRACE ifdefs from inside functions Daniel Bristot de Oliveira
2021-10-29 19:00 ` [PATCH V8 9/9] tracing/osnoise: Remove PREEMPT_RT " Daniel Bristot de Oliveira
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=cover.1635533292.git.bristot@kernel.org \
--to=bristot@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=jkacur@redhat.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=williams@redhat.com \
--cc=zanussi@kernel.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