[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20231024143908.GA40044@noisy.programming.kicks-ass.net>
Date: Tue, 24 Oct 2023 16:39:08 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Liangliang Li <liliangliang@...o.com>
Cc: Ingo Molnar <mingo@...hat.com>, Juri Lelli <juri.lelli@...hat.com>,
Vincent Guittot <vincent.guittot@...aro.org>,
Dietmar Eggemann <dietmar.eggemann@....com>,
Steven Rostedt <rostedt@...dmis.org>,
Ben Segall <bsegall@...gle.com>, Mel Gorman <mgorman@...e.de>,
Daniel Bristot de Oliveira <bristot@...hat.com>,
Valentin Schneider <vschneid@...hat.com>,
linux-kernel@...r.kernel.org, opensource.kernel@...o.com
Subject: Re: [PATCH] freezer,sched: Report TASK_FROZEN tasks as
TASK_UNINTERRUPTIBLE
On Mon, Oct 23, 2023 at 09:57:35PM +0800, Liangliang Li wrote:
> TASK_FROZEN is not in TASK_REPORT, thus a frozen task will appear as
> state == 0, IOW TASK_RUNNING.
>
> Fix this by make TASK_FROZEN appear as TASK_UNINTERRUPTIBLE, thus we
> dont need to imply a new state to userspace tools.
Who or what is seeing this and caring about the result?
Powered by blists - more mailing lists