On Fri, Apr 23 2021 at 12:50, Thomas Gleixner wrote:
On Thu, Apr 22 2021 at 17:10, John Garry wrote:So one thing I forgot to ask is:
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.
Is the thread simply stuck in the while() loop forever or is
this just an endless hardirq/thread/hardirq/thread stream?