linux-kernel - Re: Question on threaded handlers for managed interrupts

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <871rb1w3x8.ffs@nanos.tec.linutronix.de>
Date:   Fri, 23 Apr 2021 15:01:23 +0200
From:   Thomas Gleixner <tglx@...utronix.de>
To:     John Garry <john.garry@...wei.com>
Cc:     "linux-kernel\@vger.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>
Subject: Re: Question on threaded handlers for managed interrupts

John,

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.

So one thing I forgot to ask is:

Is the thread simply stuck in the while() loop forever or is
this just an endless hardirq/thread/hardirq/thread stream?

Thanks,

        tglx