The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Xiang Gao <gxxa03070307@gmail.com>,
	mhiramat@kernel.org, mingo@redhat.com, juri.lelli@redhat.com,
	vincent.guittot@linaro.org, mathieu.desnoyers@efficios.com,
	andrii@kernel.org, mingo@kernel.org, oleg@redhat.com,
	akpm@linux-foundation.org, gmonaco@redhat.com,
	ricardo.neri-calderon@linux.intel.com,
	linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
	gaoxiang17 <gaoxiang17@xiaomi.com>
Subject: Re: [PATCH v2 1/1] tracing/sched: add 'next_policy' to trace_sched_switch
Date: Wed, 24 Sep 2025 14:45:47 +0200	[thread overview]
Message-ID: <20250924124547.GJ1386988@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20250924124107.GJ3419281@noisy.programming.kicks-ass.net>

On Wed, Sep 24, 2025 at 02:41:07PM +0200, Peter Zijlstra wrote:

> That said, you can mostly guess the policy from the prio, I mean the
> distinction between fair/batch and rr/fifo gets lots, but you can
> readily tell the difference between the fair and rt and deadline tasks.

FWIW mixing RR and FIFO tasks is asking for pain, adding tracing
information isn't going to help you restore your sanity.

  reply	other threads:[~2025-09-24 12:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1756212396.git.gaoxiang17@xiaomi.com>
2025-08-26 12:48 ` [PATCH v2 1/1] tracing/sched: add 'next_policy' to trace_sched_switch Xiang Gao
2025-09-12 14:30   ` Steven Rostedt
2025-09-24 12:41     ` Peter Zijlstra
2025-09-24 12:45       ` Peter Zijlstra [this message]
     [not found] <cover.1755920363.git.gaoxiang17@xiaomi.com>
2025-08-23  3:45 ` Xiang Gao

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=20250924124547.GJ1386988@noisy.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=andrii@kernel.org \
    --cc=gaoxiang17@xiaomi.com \
    --cc=gmonaco@redhat.com \
    --cc=gxxa03070307@gmail.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=oleg@redhat.com \
    --cc=ricardo.neri-calderon@linux.intel.com \
    --cc=rostedt@goodmis.org \
    --cc=vincent.guittot@linaro.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