* Fix interrupt clearing in kdump shutdown sequence
@ 2006-09-12 12:18 Mohan Kumar M
2006-09-14 3:07 ` Michael Ellerman
0 siblings, 1 reply; 2+ messages in thread
From: Mohan Kumar M @ 2006-09-12 12:18 UTC (permalink / raw)
To: linuxppc-dev, fastboot, mingo, torvalds, paulus
Hi,
Some times HVC console on a PPC machine may have pending interrupts and
in this case kdump shutdown sequence created problem by calling
chip->end. This should be chip->eoi(). The attached patch fixes this
issue. Tested on POWER5 box.
Patch generated on 2.6.18-rc6-git4.
It will be helpful if this patch is included in 2.6.18.
Regards,
Mohan.
Call chip->eoi(irq) to clear any pending interrupt in case of kdump shutdown
sequence. chip->end(irq) does not solve this purpose.
Signed-off-by: Mohan Kumar M <mohan@in.ibm.com>
---
linux-2.6.18-rc6-git4/arch/powerpc/kernel/crash.c | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff -puN linux-2.6.18-rc6-git4/arch/powerpc/kernel/crash.c~kdump-irq-fix linux-2.6.18-rc6-git4/arch/powerpc/kernel/crash.c
--- kernel/linux-2.6.18-rc6-git4/arch/powerpc/kernel/crash.c~kdump-irq-fix 2006-09-12 17:20:39.000000000 +0530
+++ kernel-mohan/linux-2.6.18-rc6-git4/arch/powerpc/kernel/crash.c 2006-09-12 17:20:51.000000000 +0530
@@ -295,7 +295,7 @@ void default_machine_crash_shutdown(stru
struct irq_desc *desc = irq_desc + irq;
if (desc->status & IRQ_INPROGRESS)
- desc->chip->end(irq);
+ desc->chip->eoi(irq);
if (!(desc->status & IRQ_DISABLED))
desc->chip->disable(irq);
_
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Fix interrupt clearing in kdump shutdown sequence
2006-09-12 12:18 Fix interrupt clearing in kdump shutdown sequence Mohan Kumar M
@ 2006-09-14 3:07 ` Michael Ellerman
0 siblings, 0 replies; 2+ messages in thread
From: Michael Ellerman @ 2006-09-14 3:07 UTC (permalink / raw)
To: mohan; +Cc: linuxppc-dev, mingo, paulus, torvalds, fastboot
[-- Attachment #1: Type: text/plain, Size: 821 bytes --]
On Tue, 2006-09-12 at 17:48 +0530, Mohan Kumar M wrote:
> Hi,
>
> Some times HVC console on a PPC machine may have pending interrupts and
> in this case kdump shutdown sequence created problem by calling
> chip->end. This should be chip->eoi(). The attached patch fixes this
> issue. Tested on POWER5 box.
Nice catch.
Looks like chip->end() used to == xics_end_irq(), but that vanished and
became xics_eio_(direct|lpar) and got hooked up to chip->eoi(). We
should check there are no other callers of chip->end() which really want
chip->eoi().
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2006-09-14 3:07 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-09-12 12:18 Fix interrupt clearing in kdump shutdown sequence Mohan Kumar M
2006-09-14 3:07 ` Michael Ellerman
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).