From: Thomas Gleixner <tglx@linutronix.de>
To: "jeffy.chen" <jeffy.chen@rock-chips.com>
Cc: Tomasz Figa <tfiga@chromium.org>,
LKML <linux-kernel@vger.kernel.org>,
Brian Norris <briannorris@chromium.org>,
Douglas Anderson <dianders@chromium.org>,
Marc Zyngier <marc.zyngier@arm.com>
Subject: Re: [PATCH v3] genirq: Check irq disabled & masked states in irq_shutdown
Date: Wed, 31 May 2017 01:02:51 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1705310003530.2356@nanos> (raw)
In-Reply-To: <tivl20goiv96pkmvncdkqvud.1496054861146@email.android.com>
On Mon, 29 May 2017, jeffy.chen wrote:
> i think if we want to make all irq enable/disable balance, maybe we can:
>
> 1/ only call irq_enable/disable from enable/disable_irq(change other
> irq_enable/disable to enable/disable_irq), so they would be protected by the
> refcnt(deph)
You cannot call enable/disable_irq() from places which call
irq_enable/disable() due to locking reasons.
__disable_irq()/__enable_irq() can/must be called with desc->lock held, but
__enable_irq() does more than just calling irq_enable().
So no, it's not that simple.
> 2/ disable lazy stuff in irq_shoutdown(we already did this in free_irq)
No, irq_shutdown() is called from other places as well.
> 3/ in irq_shutdown, set depth to 0 if it's not disabled and masked(for lazy stuff)
> before calling disable_irq,
Uurgh, no. That's a unholy hack.
So what should be done to fix this is to make consequent use of the state bits.
irq_disable()
if (irqd_irq_disabled())
return;
irqd_set_irq_disabled();
....
This should be done for both mask/unmask disable/enable. You get the idea.
We probably want a third state bit for STARTED_UP and do the same dance in
startup/shutdown as well. Which brings me to a different issue, which is
outside the scope of your problem, but looking at the code made me find it.
If a interrupt is marked IRQ_NOAUTOEN then request_irq() will not invoke
irq_startup(). The interrupt is just completely set up, but stays disabled.
It is enabled later via enable_irq(). That works so far with no complaints,
but there is an interesting twist:
In that NOAUTOEN case nothing ever calls irq_startup() on that irq, which
means that in case the irq_chip has a irq_startup() callback nothing will
invoke it and also irq_domain_activate_irq() will never be invoked on such
an irq.
Looks like all implementations which use IRQ_NOAUTOEN are not sensitive to
that. It's been broken forever.
Fixing this needs the extra state bit IRQD_ STARTED_UP as we cannot reuse
the IRQD_ACTIVATED bit because some of the interrupts are actually
activated before they are requested.
Too tired to fix that now, but I'll have a look tomorrow. Once this is
fixed, you can add the extra bits to prevent this disable/enable calls
which cause the imbalance deeper down.
Thanks,
tglx
next prev parent reply other threads:[~2017-05-30 23:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-27 10:05 Jeffy Chen
2017-05-27 11:12 ` Thomas Gleixner
2017-05-27 15:11 ` Tomasz Figa
2017-05-29 6:56 ` Thomas Gleixner
[not found] ` <tivl20goiv96pkmvncdkqvud.1496054861146@email.android.com>
2017-05-30 23:02 ` Thomas Gleixner [this message]
2017-06-26 6:22 ` jeffy
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=alpine.DEB.2.20.1705310003530.2356@nanos \
--to=tglx@linutronix.de \
--cc=briannorris@chromium.org \
--cc=dianders@chromium.org \
--cc=jeffy.chen@rock-chips.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=tfiga@chromium.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®