From: Thomas Gleixner <tglx@linutronix.de>
To: Marc Zyngier <marc.zyngier@arm.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
x86@kernel.org, Robert Hodaszi <Robert.Hodaszi@digi.com>,
Vadim Pasternak <vadimp@mellanox.com>,
Ido Schimmel <idosch@mellanox.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-serial@vger.kernel.org
Subject: Re: [patch 1/5] genirq: Delay deactivation in free_irq()
Date: Fri, 28 Jun 2019 11:28:22 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1906281126290.1802@nanos.tec.linutronix.de> (raw)
In-Reply-To: <0bb6aae3-744b-7752-04ec-9a0e68fb86e6@arm.com>
Marc,
On Fri, 28 Jun 2019, Marc Zyngier wrote:
> > --- a/kernel/irq/autoprobe.c
> > +++ b/kernel/irq/autoprobe.c
> > @@ -1699,6 +1700,7 @@ static struct irqaction *__free_irq(stru
> > /* If this was the last handler, shut down the IRQ line: */
> > if (!desc->action) {
> > irq_settings_clr_disable_unlazy(desc);
> > + /* Only shutdown. Deactivate after synchronize_irq() */
>
> synchronize_hardirq()
Correct.
> >
> > irq_release_resources(desc);
> The patch makes complete sense, so this comment is only a nit, feel free
> to ignore me: I find it a bit odd that irq_shutdown() doesn't do the
> full thing anymore, given that it is the "canonical" function, and that
> __free_irq is the only one that has special needs. Suggestion below.
We have pretty much the same thing with startup, so I made it symmetric.
> Irrespective of which version you prefer:
>
> Reviewed-by: Marc Zyngier <marc.zyngier@arm.com>
Thanks for looking into this!
tglx
next prev parent reply other threads:[~2019-06-28 9:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 11:13 [patch 0/5] x86/irq: Cure various interrupt issues Thomas Gleixner
2019-06-25 11:13 ` [patch 1/5] genirq: Delay deactivation in free_irq() Thomas Gleixner
2019-06-28 7:42 ` Marc Zyngier
2019-06-28 9:28 ` Thomas Gleixner [this message]
2019-06-25 11:13 ` [patch 2/5] genirq: Add optional hardware synchronization for shutdown Thomas Gleixner
2019-06-26 13:03 ` Thomas Gleixner
2019-06-28 7:59 ` Marc Zyngier
2019-06-28 9:41 ` Thomas Gleixner
2019-06-25 11:13 ` [patch 3/5] x86/ioapic: Implement irq_inflight() callback Thomas Gleixner
2019-06-25 11:13 ` [patch 4/5] x86/irq: Handle spurious interrupt after shutdown gracefully Thomas Gleixner
2019-06-25 11:13 ` [patch 5/5] x86/irq: Seperate unused system vectors from spurious entry again Thomas Gleixner
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.21.1906281126290.1802@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=Robert.Hodaszi@digi.com \
--cc=gregkh@linuxfoundation.org \
--cc=idosch@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=vadimp@mellanox.com \
--cc=x86@kernel.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®