From: Tony Lindgren <tony@atomide.com>
To: Grygorii Strashko <grygorii.strashko@ti.com>
Cc: Lokesh Vutla <lokeshvutla@ti.com>, Nishanth Menon <nm@ti.com>,
linux-kernel@vger.kernel.org,
Carl-Oscar Varnander
<carl-oscar.varnander@hitachi-powergrids.com>,
linux-omap@vger.kernel.org
Subject: Re: [PATCH] bus: omap_l3_noc: mark l3 irqs as IRQF_NO_THREAD
Date: Thu, 4 Feb 2021 09:00:21 +0200 [thread overview]
Message-ID: <YBubhS4NprkdPcDM@atomide.com> (raw)
In-Reply-To: <20210128191548.4376-1-grygorii.strashko@ti.com>
* Grygorii Strashko <grygorii.strashko@ti.com> [210128 21:16]:
> The main purpose of l3 IRQs is to catch OCP bus access errors and identify
> corresponding code places by showing call stack, so it's important to
> handle L3 interconnect errors as fast as possible. On RT these IRQs will
> became threaded and will be scheduled mach more late from the moment actual
> error occurred so showing completely useless information.
>
> Hence, mark l3 IRQs as IRQF_NO_THREAD so they will not be forced threaded
> on RT or if force_irqthreads = true.
>
> Fixes: 0ee7261c9212 ("drivers: bus: Move the OMAP interconnect driver to drivers/bus/")
Thanks applying into fixes.
Tony
parent reply other threads:[~2021-02-04 7:01 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20210128191548.4376-1-grygorii.strashko@ti.com>]
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=YBubhS4NprkdPcDM@atomide.com \
--to=tony@atomide.com \
--cc=carl-oscar.varnander@hitachi-powergrids.com \
--cc=grygorii.strashko@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=nm@ti.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.