From: Crystal Wood <crwood@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Tomas Glozar <tglozar@redhat.com>, John Kacur <jkacur@redhat.com>,
linux-trace-kernel@vger.kernel.org,
Crystal Wood <crwood@redhat.com>
Subject: [PATCH v6 0/10] tracing/osnoise: Synchronization fixes
Date: Wed, 28 Oct 2026 17:01:10 -0500 [thread overview]
Message-ID: <20261028220120.4005187-1-crwood@redhat.com> (raw)
Various improvements to synchronization in osnoise/timerlat.
v6:
- Revived the "Always check OSN_WORKLOAD" and "Split out per-cpu
variable resets" patches, with fixes, to address minor issues raised
by Sashiko
- Other minor Sashiko-requseted fixes
v5:
- Removed "Split out per-cpu variable resets" due to Sashiko feedback
about races with NMIs and other tracing hooks; the main motivation
for that patch was problems with osn->sampling and tlat->thread,
both of which are now explicitly cleared.
- Fixed some patch shuffling bugs in fd detachment that were revealed
by dropping the reset patch
- Added "Start all eligible cpus from hotplug workfn"
- Removed "Always check OSN_WORKLOAD" which is no longer needed after the
hotplug workfn patch
https://lore.kernel.org/all/20261024015614.3095251-1-crwood@redhat.com/
v4: fixed a problem with the v3 fix spotted by Sashiko
https://lore.kernel.org/all/20261014220759.908839-1-crwood@redhat.com/
v3: make sure osn->sampling gets cleared on stop, even for non-workload
osnoise (reported by Sashiko)
https://lore.kernel.org/all/20261014022640.695786-1-crwood@redhat.com/
v2: addresses issues raised by Sashiko, as well as a few more problems
discovered in additional testing.
https://lore.kernel.org/all/20261010022338.2507589-1-crwood@redhat.com/
v1: https://lore.kernel.org/all/20260824211544.3984835-1-crwood@redhat.com/
Crystal Wood (10):
tracing/osnoise: Variable cleanup
tracing/osnoise: start_kthread: Always check OSN_WORKLOAD
tracing/osnoise: Start all eligible cpus from hotplug workfn
tracing/osnoise: Hold a ref on osn->kthread
tracing/osnoise: Per-cpu mutexes and fd detachment
tracing/osnoise: Split out per-cpu variable resets
tracing/osnoise: kthreads: Verify CPU after migrate_disable()
tracing/osnoise: Take trace_types_lock in timerlat_fd_open
tracing/osnoise: Print taint message for timerlat
tracing/osnoise: Refuse timerlat fd open if tracer inactive
Documentation/trace/timerlat-tracer.rst | 5 +-
kernel/trace/trace_osnoise.c | 480 ++++++++++++++----------
2 files changed, 287 insertions(+), 198 deletions(-)
--
2.54.0
next reply other threads:[~2026-10-28 22:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 22:01 Crystal Wood [this message]
2026-10-28 22:01 ` [PATCH v6 01/10] tracing/osnoise: Variable cleanup Crystal Wood
2026-10-28 22:01 ` [PATCH v6 02/10] tracing/osnoise: start_kthread: Always check OSN_WORKLOAD Crystal Wood
2026-10-28 22:06 ` sashiko-bot
2026-10-28 22:01 ` [PATCH v6 03/10] tracing/osnoise: Start all eligible cpus from hotplug workfn Crystal Wood
2026-10-28 22:01 ` [PATCH v6 04/10] tracing/osnoise: Hold a ref on osn->kthread Crystal Wood
2026-10-28 22:01 ` [PATCH v6 05/10] tracing/osnoise: Per-cpu mutexes and fd detachment Crystal Wood
2026-10-28 22:20 ` sashiko-bot
2026-10-28 22:01 ` [PATCH v6 06/10] tracing/osnoise: Split out per-cpu variable resets Crystal Wood
2026-10-28 22:24 ` sashiko-bot
2026-10-28 22:01 ` [PATCH v6 07/10] tracing/osnoise: kthreads: Verify CPU after migrate_disable() Crystal Wood
2026-10-28 22:01 ` [PATCH v6 08/10] tracing/osnoise: Take trace_types_lock in timerlat_fd_open Crystal Wood
2026-10-28 22:01 ` [PATCH v6 09/10] tracing/osnoise: Print taint message for timerlat Crystal Wood
2026-10-28 22:01 ` [PATCH v6 10/10] tracing/osnoise: Refuse timerlat fd open if tracer inactive Crystal Wood
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=20261028220120.4005187-1-crwood@redhat.com \
--to=crwood@redhat.com \
--cc=jkacur@redhat.com \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglozar@redhat.com \
/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