From: Thomas Gleixner <tglx@linutronix.de>
To: Adrian-Ken Rueegsegger <ken@codelabs.ch>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] genirq: Only call irq_ack if implemented by chip
Date: Tue, 21 Apr 2015 14:20:22 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.11.1504211408300.13914@nanos> (raw)
In-Reply-To: <552E31F8.5090407@codelabs.ch>
On Wed, 15 Apr 2015, Adrian-Ken Rueegsegger wrote:
> To support PCI MSI(-X), we register our own platform-specific MSI
> operations (x86_msi.setup_msi_irqs, etc) and implement an irq_chip that
> simply provides the irq_mask and irq_unmask operations (by reusing the
> "regular" mask_msi_irq/unmask_msi_irq).
But why are you using the edge flow handler then?
> After encountering a null pointer dereference due to the irq_chip not
> providing an irq_ack operation, I examined the commit that changed the
> source of the irq_ack call, noticing that only the check in
> handle_edge_irq was dropped while the other call sites were kept. As the
> commit message did not provide me with additional information for that
> particular fragment of the change, I (prematurely) concluded that it was
> not intentional.
>
> If it is a prerequisite for IRQ chips to provide the irq_ack operation
> when used in conjunction with handle_edge_irq, then please ignore my
> patch. In that case, I will adjust our chip implementation
> accordingly.
Yes, it is more or less. And I really want to avoid the extra
conditional in the handler hotpath.
Thanks,
prev parent reply other threads:[~2015-04-21 12:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-14 10:29 Adrian-Ken Rueegsegger
2015-04-14 18:00 ` Thomas Gleixner
2015-04-15 9:40 ` Adrian-Ken Rueegsegger
2015-04-21 12:20 ` Thomas Gleixner [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=alpine.DEB.2.11.1504211408300.13914@nanos \
--to=tglx@linutronix.de \
--cc=ken@codelabs.ch \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®