[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <42e399d7-6b50-1669-b740-cf63620c30e1@huawei.com>
Date: Fri, 21 May 2021 13:46:22 +0100
From: John Garry <john.garry@...wei.com>
To: Thomas Gleixner <tglx@...utronix.de>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Marc Zyngier" <maz@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
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>,
"Ingo Molnar" <mingo@...nel.org>, Ming Lei <ming.lei@...hat.com>
Subject: Re: Question on threaded handlers for managed interrupts
+
Hi Thomas,
On 23/04/2021 14:01, Thomas Gleixner wrote:
> On Fri, Apr 23 2021 at 12:50, Thomas Gleixner wrote:
>> On Thu, Apr 22 2021 at 17:10, John Garry wrote:
>> OTOH, the way how you splitted the handling into hard/thread context
>> provides already the base for this.
>>
>> The missing piece is infrastructure at the irq/scheduler core level to
>> handle this transparently.
>>
>> I have some horrible ideas how to solve that, but I'm sure the scheduler
>> wizards can come up with a reasonable and generic solution.
JFYI, A performance-related fix was recently added in the block layer,
and I can no longer reproduce this hang.
But I have no reason to say that it no longer exists.
Thanks,
John
Powered by blists - more mailing lists