From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Petr Malat <oss@malat.biz>
Cc: linux-kernel@vger.kernel.org, paulmck@kernel.org,
tglx@linutronix.de, nsaenzju@redhat.com, frederic@kernel.org
Subject: Re: [PATCH] softirq: Do not loop if running under a real-time task
Date: Wed, 7 Aug 2024 17:32:30 +0200 [thread overview]
Message-ID: <20240807153230.rDSKGnY9@linutronix.de> (raw)
In-Reply-To: <CANMuvJk95Ui09wZ89OrjJeOF5ySx5xO4+sS5Nd8af2wgaXgt=w@mail.gmail.com>
On 2024-07-25 08:44:02 [+0000], Petr Malat wrote:
> Hi Sebastian,
Hi Petr,
> what is the status of this softirq issue? By looking on the current
> upstream code, I think the problem is still there. I can resend my
> patch or rework it to use independent task struct flag to decide if
> softirq processing should be skipped in the current thread.
I was re-reading the thread. I don't see how the migration thread should
run softirqs. This should not happen or please show how if so.
Your example has a long running timer callback which probably gets
PI-boosted by a threaded-IRQ. The longterm plan is that long running
timer callbacks don't affect threaded interrupts as they do now.
The worked started with
c5bcab7558220 ("locking/local_lock: Add local nested BH locking infrastructure.")
https://git.kernel.org/torvalds/c/c5bcab7558220
and needs to continue.
> BR,
> Petr
Sebastian
prev parent reply other threads:[~2024-08-07 15:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 15:45 Petr Malat
2023-03-08 9:14 ` Sebastian Andrzej Siewior
2023-03-09 13:03 ` Petr Malat
2024-07-25 8:44 ` Petr Malat
2024-08-07 15:32 ` Sebastian Andrzej Siewior [this message]
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=20240807153230.rDSKGnY9@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nsaenzju@redhat.com \
--cc=oss@malat.biz \
--cc=paulmck@kernel.org \
--cc=tglx@linutronix.de \
/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®