linux-trace-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Jorge Merlino <jorge.merlino@canonical.com>
Cc: linux-trace-users@vger.kernel.org
Subject: Re: Kernelshark latency field
Date: Fri, 31 Oct 2025 11:45:32 -0400	[thread overview]
Message-ID: <20251031114532.37f30c8a@gandalf.local.home> (raw)
In-Reply-To: <fe35c5eb-7132-4203-9d6f-0a8272b114fa@canonical.com>

On Fri, 31 Oct 2025 11:52:59 -0300
Jorge Merlino <jorge.merlino@canonical.com> wrote:

> Hi folks,
> 
> I've been using kernelshark 2.2.1 and have noticed that the latency 
> field on the grid has five chars in it. The documentation [1] only 
> mention 4 fields. Anyone knows what the fifth is for?

Ah thanks for letting us know. I should update the documentation.

The fifth field is "migration disabled counter". It still allows the task
to be preempted by another task, but it will temporarily pin that task to
the CPU. It's a new feature to the Linux kernel and was introduced in 5.11.

-- Steve

      reply	other threads:[~2025-10-31 15:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-31 14:52 Kernelshark latency field Jorge Merlino
2025-10-31 15:45 ` Steven Rostedt [this message]

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=20251031114532.37f30c8a@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=jorge.merlino@canonical.com \
    --cc=linux-trace-users@vger.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).