Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1226287

Re: Regression by 01f779f4862b ("irqchip/GIC: Don't deactivate interrupts forwarded to a guest")

From Marc Zyngier <marc.zyngier@arm.com>
Newsgroups linux.kernel
Subject Re: Regression by 01f779f4862b ("irqchip/GIC: Don't deactivate interrupts forwarded to a guest")
Date 2015-09-16 19:00 +0200
Message-ID <q9odQ-1QO-19@gated-at.bofh.it> (permalink)
References <q9nUv-1tZ-37@gated-at.bofh.it> <q9o4b-1G6-13@gated-at.bofh.it>
Organization ARM Ltd

Show all headers | View raw


On 16/09/15 17:43, Jisheng Zhang wrote:
> Hi Marc,
> 
> On Thu, 17 Sep 2015 00:32:02 +0800
> Jisheng Zhang <jszhang@marvell.com> 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
> 
> The regression phenomenon is all cascaded irq can't be handled correctly.
> 
> Thanks,
> Jisheng
> 
>> 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.

This logic is only for secondary GICs, and doesn't make any sense
for another interrupt controller.

More importantly, I don't quite understand how this:

 static void gic_eoimode1_eoi_irq(struct irq_data *d)
 {
+       /* Do not deactivate an IRQ forwarded to a vcpu. */
+       if (forwarded_irq(d))
+               return;
+
        writel_relaxed(gic_irq(d), gic_cpu_base(d) + GIC_CPU_DEACTIVATE);
 }

can break any system since there is no caller of the forwarding API
just yet. Can you pinpoint why part of the patch breaks your system?
Is any code calling the irq_set_vcpu_affinity() function?

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Regression by 01f779f4862b ("irqchip/GIC: Don't deactivate  interrupts forwarded to a guest") Jisheng Zhang <jszhang@marvell.com> - 2015-09-16 18:40 +0200
  Re: Regression by 01f779f4862b ("irqchip/GIC: Don't deactivate  interrupts forwarded to a guest") Jisheng Zhang <jszhang@marvell.com> - 2015-09-16 18:50 +0200
    Re: Regression by 01f779f4862b ("irqchip/GIC: Don't deactivate interrupts  forwarded to a guest") Marc Zyngier <marc.zyngier@arm.com> - 2015-09-16 19:00 +0200
  Re: Regression by 01f779f4862b ("irqchip/GIC: Don't deactivate  interrupts forwarded to a guest") Thomas Gleixner <tglx@linutronix.de> - 2015-09-16 19:00 +0200
    Re: Regression by 01f779f4862b ("irqchip/GIC: Don't deactivate  interrupts forwarded to a guest") Jisheng Zhang <jszhang@marvell.com> - 2015-09-16 19:10 +0200
      Re: Regression by 01f779f4862b ("irqchip/GIC: Don't deactivate interrupts  forwarded to a guest") Marc Zyngier <marc.zyngier@arm.com> - 2015-09-16 19:20 +0200
      Re: Regression by 01f779f4862b ("irqchip/GIC: Don't deactivate  interrupts forwarded to a guest") Jisheng Zhang <jszhang@marvell.com> - 2015-09-16 19:20 +0200
  Re: Regression by 01f779f4862b ("irqchip/GIC: Don't deactivate  interrupts forwarded to a guest") Linus Walleij <linus.walleij@linaro.org> - 2015-09-17 23:00 +0200

csiph-web