From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Gleixner Date: Thu, 22 Mar 2007 21:23:21 +0000 Subject: Re: [PATCH] Fix irqpoll on IA64 (timer interrupt != 0) Message-Id: <1174598601.10840.231.camel@localhost.localdomain> List-Id: References: <20070320150027.GA18143@strauss.suse.de> <20070322140922.a59bea5c.akpm@linux-foundation.org> In-Reply-To: <20070322140922.a59bea5c.akpm@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Andrew Morton Cc: Bernhard Walle , linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org, Ingo Molnar On Thu, 2007-03-22 at 14:09 -0700, Andrew Morton wrote: > I think the term 'timer_interrupt' is a bit generic-sounding. Would it be > better to call it irqpoll_interrupt? After all, some architecture might > want to use, umm, the keyboard interrupt to trigger IRQ polling ;) Interesting thought, but in general I have to agree. > Also, the code presently passes the magic IRQ number into the generic IRQ > code. I wonder if we'd get a more pleasing result if we were to make the > generic IRQ code call _out_ to the architecture: > Then, ia64 can implement arch_is_irqpoll_irq() and it can do whatever it > wants in there. > > The __attribute__((weak)) thing adds a little bit of overhead, but I don't > think this is a fastpath? Well, depends what you consider a fastpath. When noirqdebug = 0, it is called on every interrupt. tglx