[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250924124547.GJ1386988@noisy.programming.kicks-ass.net>
Date: Wed, 24 Sep 2025 14:45:47 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Xiang Gao <gxxa03070307@...il.com>, mhiramat@...nel.org,
mingo@...hat.com, juri.lelli@...hat.com, vincent.guittot@...aro.org,
mathieu.desnoyers@...icios.com, andrii@...nel.org, mingo@...nel.org,
oleg@...hat.com, akpm@...ux-foundation.org, gmonaco@...hat.com,
ricardo.neri-calderon@...ux.intel.com, linux-kernel@...r.kernel.org,
linux-trace-kernel@...r.kernel.org,
gaoxiang17 <gaoxiang17@...omi.com>
Subject: Re: [PATCH v2 1/1] tracing/sched: add 'next_policy' to
trace_sched_switch
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.
Powered by blists - more mailing lists