[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20210108111948.g7szdc3b46hffz24@linutronix.de>
Date: Fri, 8 Jan 2021 12:19:48 +0100
From: Sebastian Siewior <bigeasy@...utronix.de>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Ran Wang <ran.wang_1@....com>,
Thomas Gleixner <tglx@...utronix.de>,
Jiafei Pan <jiafei.pan@....com>,
linux-rt-users@...r.kernel.org, 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>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] [RFC] rt: kernel/sched/core: fix kthread_park() pending
too long when CPU un-plugged
On 2021-01-08 10:32:36 [+0100], Peter Zijlstra wrote:
> It's a single task wakeup (the caller), doing that from hardirq context
> really should not be a problem, we do lots of that in RT already.
I'm not worry about that single wakeup but about an artificial case
where you manage to accumulate multiple single wake ups in a short
time frame.
Sebastian
Powered by blists - more mailing lists