From: Christoph Hellwig <hch@lst.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-usb@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Christoph Hellwig <hch@lst.de>,
Mathias Nyman <mathias.nyman@linux.intel.com>
Subject: Re: [REGRESSION] Failed network caused by: xhci: switch to pci_alloc_irq_vectors
Date: Fri, 19 May 2017 14:46:25 +0200 [thread overview]
Message-ID: <20170519124625.GA20063@lst.de> (raw)
In-Reply-To: <20170519083721.5a415dc3@gandalf.local.home>
On Fri, May 19, 2017 at 08:37:21AM -0400, Steven Rostedt wrote:
> ktest config bisect ended with:
>
> ***************************************
> Found bad config: CONFIG_PCI_MSI
> ***************************************
Oh, that's interesting. I think there's been a bug in the !CONFIG_PCI_MSI
fallback for pci_alloc_irq_vectors since the very beginning. And it
didn't matter for any driver so far, but xhci has a very odd way
to set MSI(-X) vs legacy interrupts.
Can you try the patch below?
diff --git a/include/linux/pci.h b/include/linux/pci.h
index 33c2b0b77429..5a7fd3b6a7b9 100644
--- a/include/linux/pci.h
+++ b/include/linux/pci.h
@@ -1342,7 +1342,7 @@ pci_alloc_irq_vectors_affinity(struct pci_dev *dev, unsigned int min_vecs,
unsigned int max_vecs, unsigned int flags,
const struct irq_affinity *aff_desc)
{
- if (min_vecs > 1)
+ if (min_vecs > 1 || !(flags & PCI_IRQ_LEGACY))
return -EINVAL;
return 1;
}
next prev parent reply other threads:[~2017-05-19 12:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 3:42 [REGRESSION] Failed network caused by: xhci: switch to pci_alloc_irq_vectors Steven Rostedt
2017-05-19 5:42 ` Greg Kroah-Hartman
2017-05-19 10:08 ` Steven Rostedt
2017-05-19 12:37 ` Steven Rostedt
2017-05-19 12:46 ` Christoph Hellwig [this message]
2017-05-19 13:45 ` Steven Rostedt
2017-05-20 16:49 ` Linus Torvalds
2017-05-20 16:53 ` Christoph Hellwig
2017-05-19 8:20 ` Christoph Hellwig
2017-05-19 10:14 ` Steven Rostedt
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=20170519124625.GA20063@lst.de \
--to=hch@lst.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.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