From: Thomas Gleixner <tglx@linutronix.de>
To: Mukesh Ojha <quic_mojha@quicinc.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] genirq/chip: Fix the warn for non-SMP system
Date: Thu, 23 May 2024 22:18:49 +0200 [thread overview]
Message-ID: <877cfkffiu.ffs@tglx> (raw)
In-Reply-To: <1715887825-1031-1-git-send-email-quic_mojha@quicinc.com>
On Fri, May 17 2024 at 01:00, Mukesh Ojha wrote:
We don't fix warnings. We fix the underlying problem.
> __irq_startup_managed() for !SMP system returns IRQ_STARTUP_NORMAL
> which may result in a WARNING during enablement of an irq i.e.,
> starting a irq while it is not activated.
>
> Fix this by appropriately returning IRQ_STARTUP_MANAGED.
What does that fix?
Absolutely nothing because both cases at the call site invoke
__irq_startup() which warns if the interrupt has not been activated yet.
It's not magically activated when __irq_startup_managed() returns
IRQ_STARTUP_MANAGED.
Also if you look at the SMP variant of that function then you might
notice that IRQ_STARTUP_MANAGED is not returned unconditionally. That
function can return IRQ_STARTUP_NORMAL too.
Just for the record. There are no managed interrupts on SMP=n. The code
which can initialize them is not even compiled in.
So I have no idea why you think that this has anything to do with
managed interrupts.
What's worse is that this does not even build on UP because
irq_do_set_affinity() does not exists for SMP=n. It builds today because
the IRQ_STARTUP_MANAGED case is optimized out by the compiler.
Sigh,
tglx
prev parent reply other threads:[~2024-05-23 20:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 19:30 [PATCH] genirq/chip: Fix the warn for non-SMP system Mukesh Ojha
2024-05-17 8:48 ` kernel test robot
2024-05-17 8:58 ` kernel test robot
2024-05-23 20:18 ` Thomas Gleixner [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=877cfkffiu.ffs@tglx \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_mojha@quicinc.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.