From: Liu Hua <sdu.liu@huawei.com>
To: <tglx@linutronix.de>, <jason@lakedaemon.net>,
<nicolas.pitre@linaro.org>, <linux@arm.linux.org.uk>,
<will.deacon@arm.com>, <ebiederm@xmission.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <wangnan0@huawei.com>,
<liuxueliu.liu@huawei.com>, <peifeiyue@huawei.com>,
<liusdu@huawei.com>, Liu Hua <sdu.liu@huawei.com>
Subject: [RFC PATCH 0/2] irqchip: GIC: check and clear GIC interupt active status
Date: Fri, 11 Jul 2014 14:46:15 +0800 [thread overview]
Message-ID: <1405061177-43834-1-git-send-email-sdu.liu@huawei.com> (raw)
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
next reply other threads:[~2014-07-12 0:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 6:46 Liu Hua [this message]
2014-07-11 6:46 ` [RFC PATCH 1/2] irqchip: GIC: introduce ICPIDR2 register interface Liu Hua
2014-07-11 6:46 ` [RFC PATCH 2/2] irqchip: GIC: introduce method to deactive interupts Liu Hua
2014-07-11 12:35 ` [RFC PATCH 0/2] irqchip: GIC: check and clear GIC interupt active status Will Deacon
2014-07-14 3:22 ` Liu hua
2014-07-14 9:57 ` Will Deacon
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=1405061177-43834-1-git-send-email-sdu.liu@huawei.com \
--to=sdu.liu@huawei.com \
--cc=ebiederm@xmission.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=liusdu@huawei.com \
--cc=liuxueliu.liu@huawei.com \
--cc=nicolas.pitre@linaro.org \
--cc=peifeiyue@huawei.com \
--cc=tglx@linutronix.de \
--cc=wangnan0@huawei.com \
--cc=will.deacon@arm.com \
/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®