[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YuG1vwqs1GgE/twg@worktop.programming.kicks-ass.net>
Date: Thu, 28 Jul 2022 00:01:35 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Tejun Heo <tj@...nel.org>
Cc: Qais Yousef <qais.yousef@....com>,
Xuewen Yan <xuewen.yan@...soc.com>, rafael@...nel.org,
viresh.kumar@...aro.org, mingo@...hat.com, juri.lelli@...hat.com,
vincent.guittot@...aro.org, dietmar.eggemann@....com,
rostedt@...dmis.org, bsegall@...gle.com, mgorman@...e.de,
bristot@...hat.com, linux-kernel@...r.kernel.org,
ke.wang@...soc.com, xuewyan@...mail.com, linux-pm@...r.kernel.org,
Waiman Long <longman@...hat.com>
Subject: Re: [PATCH] sched/schedutil: Fix deadlock between cpuset and cpu
hotplug when using schedutil
On Tue, Jul 12, 2022 at 06:13:46AM -1000, Tejun Heo wrote:
> But now we're failing user-initiated operations randomly. I have a hard time
> seeing that as an acceptable solution.
There (sadly) is precedent for that; grep for "cpu_hotplug_disable".
Powered by blists - more mailing lists