[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1405061177-43834-1-git-send-email-sdu.liu@huawei.com>
Date: Fri, 11 Jul 2014 14:46:15 +0800
From: Liu Hua <sdu.liu@...wei.com>
To: <tglx@...utronix.de>, <jason@...edaemon.net>,
<nicolas.pitre@...aro.org>, <linux@....linux.org.uk>,
<will.deacon@....com>, <ebiederm@...ssion.com>
CC: <linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>, <wangnan0@...wei.com>,
<liuxueliu.liu@...wei.com>, <peifeiyue@...wei.com>,
<liusdu@...wei.com>, Liu Hua <sdu.liu@...wei.com>
Subject: [RFC PATCH 0/2] irqchip: GIC: check and clear GIC interupt active status
For this version of GIC codes, kernel assumes that all the interrupt
status of GIC is inactive. So the kernel does not check this when
booting.
This is no problem on must sitations. But when kdump is deplayed.
And a panic occurs when a interrupt is being handled (may be PPI
and SPI). We have no chance to write relative bit to GICC_EOIR.
So this interrupt remains active. And GIC will not deliver this
type interrupt to cpu interface. And the capture kernel may
fail to boot becase of lacking of certain interrupt (such as timer
interupt).
I glanced over the GIC Architecture Specification, but did not
find a simple way to deactive state of all interrupts. For GICv1,
I can only deal with one abnormal interrupt state one time. For
GICv2, I can deactive 32 one time.
So guys, Do you know a better way to do that?
Liu Hua (2):
irqchip: gic: introduce ICPIDR2 register interface
irqchip: GIC: introduce method to deactive interupts
drivers/irqchip/irq-gic.c | 57 +++++++++++++++++++++++++++++++++++++++++
include/linux/irqchip/arm-gic.h | 1 +
2 files changed, 58 insertions(+)
--
1.9.0
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists