From: jszhang@marvell.com (Jisheng Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: Regression by 01f779f4862b ("irqchip/GIC: Don't deactivate interrupts forwarded to a guest")
Date: Thu, 17 Sep 2015 01:10:21 +0800 [thread overview]
Message-ID: <20150917011021.0460792d@xhacker> (raw)
In-Reply-To: <20150917005908.111c00ca@xhacker>
Dear Thomas,
On Thu, 17 Sep 2015 00:59:08 +0800
Jisheng Zhang <jszhang@marvell.com> wrote:
> On Wed, 16 Sep 2015 18:52:41 +0200
> Thomas Gleixner <tglx@linutronix.de> wrote:
>
> > On Thu, 17 Sep 2015, Jisheng Zhang wrote:
> >
> > > Hi Marc,
> > >
> > > Commit 01f779f4862b ("irqchip/GIC: Don't deactivate interrupts forwarded to a
> > > guest") causes a regression on Marvell BG4CT SoC. In this SoC, there's only one
> > > GIC, the secondary irq controller is Synopsys DW iCtl:
> > > drivers/irqchip/irq-dw-apb-ictl.c
> > >
> > > So cascading_gic_irq() should return true on Marvell BG4CT SoC, but it returns
> > > false. The logic in cascading_gic_irq() doesn't take cascaded irq controller
> > > which is provided by non-gic controllers.
> >
> > I have a fix pending for this in
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tmp.irq
> >
> > 714665351cc7: irqchip/gic: Use IRQD_FORWARDED_TO_VCPU flag
> >
> > Can you please give that a try?
>
> Sure, Will try and get back to you
Good news! The regression is fixed, cascaded irq works again!
Feel free to add
Tested-by: Jisheng Zhang <jszhang@marvell.com>
Thanks lot for this patch,
Jisheng
next prev parent reply other threads:[~2015-09-16 17:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 16:32 Regression by 01f779f4862b ("irqchip/GIC: Don't deactivate interrupts forwarded to a guest") Jisheng Zhang
2015-09-16 16:43 ` Jisheng Zhang
2015-09-16 16:55 ` Marc Zyngier
2015-09-16 16:52 ` Thomas Gleixner
2015-09-16 16:59 ` Jisheng Zhang
2015-09-16 17:10 ` Jisheng Zhang [this message]
2015-09-16 17:16 ` Marc Zyngier
2015-09-17 20:51 ` Linus Walleij
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=20150917011021.0460792d@xhacker \
--to=jszhang@marvell.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).