From: Heiner Kallweit <hkallweit1@gmail.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
Christoph Hellwig <hch@lst.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI: let pci_request_irq properly deal with threaded interrupts
Date: Mon, 30 Jul 2018 23:50:51 +0200 [thread overview]
Message-ID: <d4666725-b459-832d-fb29-25ce930debe2@gmail.com> (raw)
In-Reply-To: <20180730213028.GC45322@bhelgaas-glaptop.roam.corp.google.com>
On 30.07.2018 23:30, Bjorn Helgaas wrote:
> [+cc Thomas, Christoph, LKML]
>
> On Mon, Jul 30, 2018 at 12:03:42AM +0200, Heiner Kallweit wrote:
>> If we have a threaded interrupt with the handler being NULL, then
>> request_threaded_irq() -> __setup_irq() will complain and bail out
>> if the IRQF_ONESHOT flag isn't set. Therefore check for the handler
>> being NULL and set IRQF_ONESHOT in this case.
>>
>> This change is needed to migrate the mei_me driver to
>> pci_alloc_irq_vectors() and pci_request_irq().
>>
>> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
>
> I'd like an ack from Thomas because this requirement about IRQF_ONESHOT
> usage isn't mentioned in the request_threaded_irq() function doc or
> Documentation/
>
Sure.
That's the related comment in __setup_irq():
* The interrupt was requested with handler = NULL, so
* we use the default primary handler for it. But it
* does not have the oneshot flag set. In combination
* with level interrupts this is deadly, because the
* default primary handler just wakes the thread, then
* the irq lines is reenabled, but the device still
* has the level irq asserted. Rinse and repeat....
*
* While this works for edge type interrupts, we play
* it safe and reject unconditionally because we can't
* say for sure which type this interrupt really
* has. The type flags are unreliable as the
* underlying chip implementation can override them.
*/
>> ---
>> drivers/pci/irq.c | 6 +++++-
>> 1 file changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/pci/irq.c b/drivers/pci/irq.c
>> index 2a808e10..a1de501a 100644
>> --- a/drivers/pci/irq.c
>> +++ b/drivers/pci/irq.c
>> @@ -86,13 +86,17 @@ int pci_request_irq(struct pci_dev *dev, unsigned int nr, irq_handler_t handler,
>> va_list ap;
>> int ret;
>> char *devname;
>> + unsigned long irqflags = IRQF_SHARED;
>> +
>> + if (!handler)
>> + irqflags |= IRQF_ONESHOT;
>>
>> va_start(ap, fmt);
>> devname = kvasprintf(GFP_KERNEL, fmt, ap);
>> va_end(ap);
>>
>> ret = request_threaded_irq(pci_irq_vector(dev, nr), handler, thread_fn,
>> - IRQF_SHARED, devname, dev_id);
>> + irqflags, devname, dev_id);
>> if (ret)
>> kfree(devname);
>> return ret;
>> --
>> 2.18.0
>>
>
next prev parent reply other threads:[~2018-07-30 21:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d004975f-03a8-59f5-56ef-f4e1f8e12dfb@gmail.com>
2018-07-30 21:30 ` [PATCH] PCI: let pci_request_irq properly deal with threaded interrupts Bjorn Helgaas
2018-07-30 21:50 ` Heiner Kallweit [this message]
2018-07-30 21:54 ` Andy Shevchenko
2018-07-30 22:36 ` Thomas Gleixner
2018-07-31 6:15 ` Marc Zyngier
2018-08-01 19:51 ` Heiner Kallweit
2018-08-03 14:09 ` Thomas Gleixner
2018-08-03 19:25 ` Heiner Kallweit
2018-08-03 19:40 ` Thomas Gleixner
2018-08-03 20:55 ` Heiner Kallweit
2018-07-30 22:42 ` Bjorn Helgaas
2018-07-30 22:50 ` Thomas Gleixner
2018-07-31 7:29 ` Lee Jones
2018-07-31 8:01 ` Russell King - ARM Linux
2018-07-31 11:13 ` Bjorn Helgaas
2018-07-31 8:08 ` Krzysztof Kozlowski
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=d4666725-b459-832d-fb29-25ce930debe2@gmail.com \
--to=hkallweit1@gmail.com \
--cc=bhelgaas@google.com \
--cc=hch@lst.de \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=tglx@linutronix.de \
/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