Generic Linux architectural discussions
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: linux-arch@vger.kernel.org
Subject: Re: [PATCH] update generic irq for parisc
Date: Wed, 04 Oct 2006 13:14:38 +1000	[thread overview]
Message-ID: <1159931678.8469.2.camel@localhost.localdomain> (raw)
In-Reply-To: <1157827893.3462.19.camel@mulgrave.il.steeleye.com>

On Sat, 2006-09-09 at 13:51 -0500, James Bottomley wrote:
> We have had a specific problem with the current generic linux IRQ code
> for ages, in that indirection via function pointers is horribly
> expensive for us (basically, the CPU pipes stall).  We'd like to use the
> new genirq infrastructure to mitigate some of the problem.
> 
> I didn't want simply to move the irq handlers back into our arch code
> again, since that would remove all the benefits of common handling code.
> What I did was template out the common code in a way that keeps it
> common but allows an architecture to modify it (for us to put our acks
> and eoi's in as functions instead of function pointers).
> 
> If everyone is OK with this, I'll introduce a new type of interrupt with
> a specific handler (so for our heavily called interrupts like timer and
> IPI we don't even need to indirect through action->handler()).

I don't have any objection to this patch as long as the current
behaviour with function pointers still works fine (which seems to be the
case from a quick look through the patch). On PowerPC, we have a huge
variety of interrupt controllers and cascaded controllers and thus we
can't really apply your shortcut.

Ben.



      parent reply	other threads:[~2006-10-04  3:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-09 18:51 [PATCH] update generic irq for parisc James Bottomley
2006-09-09 19:16 ` James Bottomley
2006-10-04  3:14 ` Benjamin Herrenschmidt [this message]

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=1159931678.8469.2.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=James.Bottomley@steeleye.com \
    --cc=linux-arch@vger.kernel.org \
    /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