mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: David Daney <ddaney@caviumnetworks.com>
Cc: Marc Zyngier <marc.zyngier@arm.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>
Subject: Re: irq domain hierarchy vs. chaining w/ PCI MSI-X...
Date: Mon, 30 Jan 2017 14:32:02 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1701301430450.3606@nanos> (raw)
In-Reply-To: <6e6c3406-c4e9-1195-168b-934bbc55c6c4@caviumnetworks.com>

On Fri, 13 Jan 2017, David Daney wrote:
> At the point where the handle_*_irq() functions call handle_irq_event(), we
> need to 9optionally) do something both immediately before and after the call
> to handle_irq_event().
> 
> In irq_chip add a function:
> 
>     void (*irq_handle)(struct irq_data *data, struct irq_desc *desc);
> 
> Really this is the per irq_chip flow handler.
> 
> Then in handle_fasteoi_irq() and probably the other flow handlers as well:
> 
>    .
>    .
>    .
>    if (chip->irq_handle)
>       chip->irq_handle(&desc->irq_data, desc);
>    else
>       handle_irq_event(desc);
>    .
>    .
>    .
> 
> Those 4 lines of code could be factored out into a helper function in chip.c


And why don't you just write a flow handler function which does exactly
what you need instead of adding more conditionals into all hotpath
functions?

Thanks,

	tglx

  reply	other threads:[~2017-01-30 13:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-12 22:35 David Daney
2017-01-13 15:41 ` Linus Walleij
2017-01-13 16:15 ` Marc Zyngier
2017-01-13 17:37   ` David Daney
2017-01-13 18:45     ` Marc Zyngier
2017-01-13 19:40       ` David Daney
2017-01-30 13:32         ` Thomas Gleixner [this message]
2017-01-30 17:55           ` David Daney

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=alpine.DEB.2.20.1701301430450.3606@nanos \
    --to=tglx@linutronix.de \
    --cc=ddaney@caviumnetworks.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.zyngier@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®