[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YHryaegfV9jo6aiL@hirez.programming.kicks-ass.net>
Date: Sat, 17 Apr 2021 16:36:25 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: zhouchuangao <zhouchuangao@...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>,
Andrew Morton <akpm@...ux-foundation.org>,
Kees Cook <keescook@...omium.org>,
Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
Michal Hocko <mhocko@...e.com>,
"Guilherme G. Piccoli" <gpiccoli@...onical.com>,
Vlastimil Babka <vbabka@...e.cz>,
Lukas Bulwahn <lukas.bulwahn@...il.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kernel/hung_task: Add a whitelist and blacklist
mechanism.
On Sat, Apr 17, 2021 at 07:13:01AM -0700, zhouchuangao wrote:
> eg:
> In Android system, we usually and some processes to the whitelist.
> static task_t task_whitelist[] = {
> {"mdrt_thread", HUNG_TASK_WHITELIST},
> {"chre_kthread", HUNG_TASK_WHITELIST},
> {"scp_power_reset", HUNG_TASK_WHITELIST},
> {"ccci_fsm1", HUNG_TASK_WHITELIST},
> {"qos_ipi_recv", HUNG_TASK_WHITELIST},
> {NULL, 0},
> };
What are these tasks doing that the hung-task detector fires on them?
Should you fix that instead?
Powered by blists - more mailing lists