From: Steven Rostedt <rostedt@goodmis.org>
To: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>,
linux-rt-users@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Vladimir Oltean <vladimir.oltean@nxp.com>,
Esben Haabendal <esben@geanix.com>
Subject: Re: commit 3d5bfbd97163 versus -rt
Date: Tue, 15 Jun 2021 13:09:59 -0400 [thread overview]
Message-ID: <20210615130959.1de1f52a@gandalf.local.home> (raw)
In-Reply-To: <37e28373-c6ec-2602-ec5c-cb0b65ce6697@prevas.dk>
On Tue, 15 Jun 2021 18:24:20 +0200
Rasmus Villemoes <rasmus.villemoes@prevas.dk> wrote:
> > ~ # uname -r
> > 5.10.42-00001-g10216cf63a12
> > ~ # grep -ow threadirqs /proc/cmdline
> > threadirqs
> > ~ # zcat /proc/config.gz | grep FORCED_THREADING
> > CONFIG_IRQ_FORCED_THREADING=y
> > ~ # dmesg | grep WARNING
> > ~ #
>
> And as an extra data point, it also doesn't trigger on 5.10.41-rt42
> configured without PREEMPT_RT but with threadirqs on the command line.
Sounds to me that there's a "spin_lock_irq*" somewhere in the path, because
from what I can see, there's not much difference with the IRQ code between
5.10.41 and 5.10.41-rt42. But if you are seeing it only with PREEMPT_RT
set, that tells me that without PREEMPT_RT, interrupts are disabled at that
point, but not with PREEMPT_RT. The only thing I can think of that would do
that is a spin_lock_irq*() taken (not a raw_spin_lock_irq*()).
-- Steve
next prev parent reply other threads:[~2021-06-15 17:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 12:35 commit 3d5bfbd97163 versus -rt Rasmus Villemoes
2021-06-15 15:33 ` Steven Rostedt
2021-06-15 15:57 ` Rasmus Villemoes
2021-06-15 16:24 ` Rasmus Villemoes
2021-06-15 17:09 ` Steven Rostedt [this message]
2021-06-16 8:00 ` Oleksandr Natalenko
2021-06-18 20:04 ` Thomas Gleixner
2021-06-21 7:54 ` Rasmus Villemoes
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=20210615130959.1de1f52a@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=bgolaszewski@baylibre.com \
--cc=esben@geanix.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rasmus.villemoes@prevas.dk \
--cc=vladimir.oltean@nxp.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.