mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: John Garry <john.garry@huawei.com>
Cc: "linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Marc Zyngier <maz@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Juri Lelli <juri.lelli@redhat.com>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
	Daniel Bristot de Oliveira <bristot@redhat.com>,
	Ingo Molnar <mingo@kernel.org>
Subject: Re: Question on threaded handlers for managed interrupts
Date: Fri, 23 Apr 2021 15:01:23 +0200	[thread overview]
Message-ID: <871rb1w3x8.ffs@nanos.tec.linutronix.de> (raw)
In-Reply-To: <874kfxw9zv.ffs@nanos.tec.linutronix.de>

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

  parent reply	other threads:[~2021-04-23 13:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-22 16:10 John Garry
2021-04-23 10:50 ` Thomas Gleixner
2021-04-23 12:02   ` John Garry
2021-04-23 13:01   ` Thomas Gleixner [this message]
2021-04-23 15:00     ` John Garry
2021-05-21 12:46     ` John Garry

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871rb1w3x8.ffs@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=bristot@redhat.com \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=john.garry@huawei.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=vincent.guittot@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®