From: Daniel Bristot de Oliveira <bristot@kernel.org>
To: linux-kernel@vger.kernel.org, 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>,
linux-trace-devel@vger.kernel.org
Subject: [PATCH 0/5] osnoise: Support multiple instances
Date: Thu, 12 Aug 2021 15:57:19 +0200 [thread overview]
Message-ID: <cover.1628775552.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.
Daniel Bristot de Oliveira (5):
trace/osnoise: Do not follow tracing_cpumask
trace/osnoise: Split workload start from the tracer start
trace/osnoise: Use start/stop_per_cpu_kthreads() on
osnoise_cpus_write()
trace/osnoise: Support a list of trace_array *tr
trace/osnoise: Allow multiple instances of the same tracer
kernel/trace/trace_osnoise.c | 410 ++++++++++++++++++++++++-----------
1 file changed, 289 insertions(+), 121 deletions(-)
--
2.31.1
next reply other threads:[~2021-08-12 14:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 13:57 Daniel Bristot de Oliveira [this message]
2021-08-12 13:57 ` [PATCH 1/5] trace/osnoise: Do not follow tracing_cpumask Daniel Bristot de Oliveira
2021-08-12 13:57 ` [PATCH 2/5] trace/osnoise: Split workload start from the tracer start Daniel Bristot de Oliveira
2021-08-12 13:57 ` [PATCH 3/5] trace/osnoise: Use start/stop_per_cpu_kthreads() on osnoise_cpus_write() Daniel Bristot de Oliveira
2021-08-12 13:57 ` [PATCH 4/5] trace/osnoise: Support a list of trace_array *tr Daniel Bristot de Oliveira
2021-08-12 13:57 ` [PATCH 5/5] trace/osnoise: Allow multiple instances of the same tracer 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.1628775552.git.bristot@kernel.org \
--to=bristot@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--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;
as well as URLs for NNTP newsgroup(s).