All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <steven@rostedt.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Crystal Wood <crwood@redhat.com>,
	Tomas Glozar <tglozar@redhat.com>, John Kacur <jkacur@redhat.com>
Subject: [GIT PULL] tracing latency: Updates for 7.2
Date: Tue, 16 Jun 2026 02:24:22 -0400	[thread overview]
Message-ID: <20260616022422.347d69f3@fedora> (raw)


Linus,

tracing latency updates for 7.2:

- Dump the stack to the buffer on timerlat uret threashold event

  Record the stack trace in the buffer for THREAD_URET as well as
  THREAD_CONTEXT when the threshold is hit. Otherwise, if the threshold was
  not hit at task wakeup, but was at task return, it will not produce a
  stack trace making it harder to debug.

- Have osnoise trace prints print to all buffers

  The osnoise tracer is allowed to print to the main buffer. Add a
  osnoise_print() helper function and use trace_array_vprintk() to print
  osnoise output.


Please pull the latest trace-latency-v7.2 tree, which can be found at:


  git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
trace-latency-v7.2

Tag SHA1: c26d17d6a9044bac1a36f496013af9816aed3ae2
Head SHA1: 9cb99c598643ba78638dfd668cf020544159cf70


Crystal Wood (2):
      tracing/osnoise: Dump stack on timerlat uret threshold event
      tracing/osnoise: Array printk init and cleanup

----
 kernel/trace/trace_osnoise.c | 46 ++++++++++++++++++++++++++++----------------
 1 file changed, 29 insertions(+), 17 deletions(-)
---------------------------

                 reply	other threads:[~2026-06-16  6:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20260616022422.347d69f3@fedora \
    --to=steven@rostedt.org \
    --cc=crwood@redhat.com \
    --cc=jkacur@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglozar@redhat.com \
    --cc=torvalds@linux-foundation.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.