[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTikVHO9DmyTX==CwViDK1rP0masBwjMakHZ0U=kZ@mail.gmail.com>
Date: Mon, 27 Sep 2010 10:36:16 -0700
From: Tony Luck <tony.luck@...el.com>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: LKML <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Ingo Molnar <mingo@...e.hu>,
Peter Zijlstra <peterz@...radead.org>,
Christoph Hellwig <hch@...radead.org>,
linux-alpha@...r.kernel.org, linux-cris-kernel@...s.com,
Haavard Skinnemoen <hskinnemoen@...el.com>,
linux-ia64@...r.kernel.org,
Yoshinori Sato <ysato@...rs.sourceforge.jp>,
Hirokazu Takata <takata@...ux-m32r.org>,
Greg Ungerer <gerg@...inux.org>, Jeff Dike <jdike@...toit.com>,
linux-parisc@...r.kernel.org, Chris Zankel <chris@...kel.net>,
linux-arch@...r.kernel.org
Subject: Re: [RFC trollpatch 1/1] genirq: Remove the fits all and nothing
__do_IRQ() code
On Wed, Sep 8, 2010 at 11:14 AM, Thomas Gleixner <tglx@...utronix.de> wrote:
> The following architectures are still using __do_IRQ():
>
> alpha, cris, ia64, h8300, m32r, m68knommu, parisc, um
Thomas,
I (belatedly) took a look at fixing ia64 ... but I've run into a small snag.
The __do_IRQ() routine makes a call to:
desc->chip->end(irq);
while neither of the "handle_level_irq()" nor "handle_edge_irq()"
functions do this.
On ia64 iosapic_end_level_irq() call iosapic_eoi() for me. Without it
my system hangs during boot (with some driver timeout complaining
about dropped interrupts).
Is the omission of desc->chip->end(irq); deliberate? In which case
I need to find another place to call iosapic_eoi(). Or is it accidental?
Thanks
-Tony
--
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