From: Christoph Hellwig <hch@lst.de>
To: Alexander Gordeev <agordeev@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>,
helgaas@kernel.org, pjw@netapp.com, axboe@fb.com,
keith.busch@intel.com, linux-pci@vger.kernel.org,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH 1/2] PCI: Provide sensible irq vector alloc/free routines
Date: Thu, 12 May 2016 09:35:52 +0200 [thread overview]
Message-ID: <20160512073552.GA4027@lst.de> (raw)
In-Reply-To: <20160511094432.GB31347@agordeev.lab.eng.brq.redhat.com>
Hi Alex,
what do you think about the incremental patch below? This should
address the concerns about the strange PPC bridges, although I don't
have a way to test one:
diff --git a/drivers/pci/msi.c b/drivers/pci/msi.c
index a510484..32ce65e 100644
--- a/drivers/pci/msi.c
+++ b/drivers/pci/msi.c
@@ -1177,6 +1177,7 @@ int pci_alloc_irq_vectors(struct pci_dev *dev, unsigned int nr_vecs,
if (WARN_ON_ONCE(dev->msi_enabled || dev->msix_enabled))
return -EINVAL;
+retry:
if (!pci_msi_supported(dev, 1))
goto use_legacy_irq;
@@ -1191,17 +1192,26 @@ int pci_alloc_irq_vectors(struct pci_dev *dev, unsigned int nr_vecs,
if (!dev->irqs)
return -ENOMEM;
- if (dev->msix_cap && !(flags & PCI_IRQ_NOMSIX))
+ if (dev->msix_cap && !(flags & PCI_IRQ_NOMSIX)) {
ret = __pci_enable_msix(dev, nr_vecs);
- else
+ if (ret < 0)
+ flags |= PCI_IRQ_NOMSIX;
+ } else {
ret = __pci_enable_msi(dev, nr_vecs);
- if (ret)
- goto out_free_irqs;
+ }
- return 0;
+ /* if we succeeded getting all vectors return the number we got: */
+ if (!ret)
+ return nr_vecs;
-out_free_irqs:
kfree(dev->irqs);
+ /* if ret is positive it's the numbers of vectors we can use, retry: */
+ if (ret > 0) {
+ nr_vecs = ret;
+ goto retry;
+ }
+
+ /* no MSI or MSI-X vectors available, fall back to the legacy IRQ: */
use_legacy_irq:
dev->irqs = &dev->irq;
return 1;
next prev parent reply other threads:[~2016-05-12 7:35 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-05 14:04 PCI: Provide sensible irq vector alloc/free routines Christoph Hellwig
2016-05-05 14:04 ` [PATCH 1/2] " Christoph Hellwig
2016-05-06 16:04 ` Bjorn Helgaas
2016-05-06 16:28 ` Christoph Hellwig
2016-05-06 16:35 ` Bjorn Helgaas
2016-05-08 9:05 ` Christoph Hellwig
2016-05-09 22:46 ` Bjorn Helgaas
2016-05-11 8:52 ` Christoph Hellwig
2016-05-16 19:39 ` Bjorn Helgaas
2016-05-17 16:45 ` Christoph Hellwig
2016-05-11 7:45 ` Alexander Gordeev
2016-05-11 8:50 ` Christoph Hellwig
2016-05-11 9:44 ` Alexander Gordeev
2016-05-12 7:35 ` Christoph Hellwig [this message]
2016-05-12 9:44 ` Alexander Gordeev
2016-05-12 11:03 ` Christoph Hellwig
2016-05-12 12:11 ` Alexander Gordeev
2016-05-12 12:19 ` Christoph Hellwig
2016-05-12 14:29 ` Christoph Hellwig
2016-05-13 8:29 ` Alexander Gordeev
2016-06-11 1:14 ` Bjorn Helgaas
2016-06-13 15:15 ` Christoph Hellwig
2016-06-21 14:33 ` Christoph Hellwig
2016-05-12 11:04 ` Alexander Gordeev
2016-05-12 11:04 ` Christoph Hellwig
2016-05-05 14:04 ` [PATCH 2/2] nvme: switch to use pci_alloc_irq_vectors Christoph Hellwig
2016-05-10 15:27 ` Keith Busch
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=20160512073552.GA4027@lst.de \
--to=hch@lst.de \
--cc=agordeev@redhat.com \
--cc=axboe@fb.com \
--cc=helgaas@kernel.org \
--cc=keith.busch@intel.com \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=pjw@netapp.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;
as well as URLs for NNTP newsgroup(s).