All of lore.kernel.org
 help / color / mirror / Atom feed
From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 1/2] PCI: Provide sensible irq vector alloc/free routines
Date: Wed, 11 May 2016 10:50:49 +0200	[thread overview]
Message-ID: <20160511085049.GA20279@lst.de> (raw)
In-Reply-To: <20160511074527.GA31347@agordeev.lab.eng.brq.redhat.com>

Hi Alexander,

> Moreover, patch 2/2 not only removed pci_enable_msi[x]_range()
> internal fallback logic (from desired number of interrupts to
> available number of interrupts), but it also removed MSI-X to
> MSI fallback.

That is done in the very begining of the function, see the quoted
part of the patch just below:

> > +	if (dev->msix_cap && !(flags & PCI_IRQ_NOMSIX))
> > +		nr_vecs = min_t(unsigned int, nr_vecs, pci_msix_vec_count(dev));
> > +	else if (dev->msi_cap)
> > +		nr_vecs = min_t(unsigned int, nr_vecs, pci_msi_vec_count(dev));
> > +	else
> > +		goto use_legacy_irq;

> > +	if (dev->msix_cap && !(flags & PCI_IRQ_NOMSIX))
> > +		ret = __pci_enable_msix(dev, nr_vecs);
> > +	else
> > +		ret = __pci_enable_msi(dev, nr_vecs);
> 
> 1. No fallbacks.

I read through the code in msi.c in detail and could not find a legitimate
case where we have msix_cap but actually fail the MSI-X allocation.  If that
is a valid case I can happily add the fallback here as well.

WARNING: multiple messages have this Message-ID (diff)
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: Wed, 11 May 2016 10:50:49 +0200	[thread overview]
Message-ID: <20160511085049.GA20279@lst.de> (raw)
In-Reply-To: <20160511074527.GA31347@agordeev.lab.eng.brq.redhat.com>

Hi Alexander,

> Moreover, patch 2/2 not only removed pci_enable_msi[x]_range()
> internal fallback logic (from desired number of interrupts to
> available number of interrupts), but it also removed MSI-X to
> MSI fallback.

That is done in the very begining of the function, see the quoted
part of the patch just below:

> > +	if (dev->msix_cap && !(flags & PCI_IRQ_NOMSIX))
> > +		nr_vecs = min_t(unsigned int, nr_vecs, pci_msix_vec_count(dev));
> > +	else if (dev->msi_cap)
> > +		nr_vecs = min_t(unsigned int, nr_vecs, pci_msi_vec_count(dev));
> > +	else
> > +		goto use_legacy_irq;

> > +	if (dev->msix_cap && !(flags & PCI_IRQ_NOMSIX))
> > +		ret = __pci_enable_msix(dev, nr_vecs);
> > +	else
> > +		ret = __pci_enable_msi(dev, nr_vecs);
> 
> 1. No fallbacks.

I read through the code in msi.c in detail and could not find a legitimate
case where we have msix_cap but actually fail the MSI-X allocation.  If that
is a valid case I can happily add the fallback here as well.

  reply	other threads:[~2016-05-11  8:50 UTC|newest]

Thread overview: 54+ 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 ` Christoph Hellwig
2016-05-05 14:04 ` [PATCH 1/2] " Christoph Hellwig
2016-05-05 14:04   ` Christoph Hellwig
2016-05-06 16:04   ` Bjorn Helgaas
2016-05-06 16:04     ` Bjorn Helgaas
2016-05-06 16:28     ` Christoph Hellwig
2016-05-06 16:28       ` Christoph Hellwig
2016-05-06 16:35       ` Bjorn Helgaas
2016-05-06 16:35         ` Bjorn Helgaas
2016-05-08  9:05         ` Christoph Hellwig
2016-05-08  9:05           ` Christoph Hellwig
2016-05-09 22:46   ` Bjorn Helgaas
2016-05-09 22:46     ` Bjorn Helgaas
2016-05-11  8:52     ` Christoph Hellwig
2016-05-11  8:52       ` Christoph Hellwig
2016-05-16 19:39     ` Bjorn Helgaas
2016-05-16 19:39       ` Bjorn Helgaas
2016-05-17 16:45       ` Christoph Hellwig
2016-05-17 16:45         ` Christoph Hellwig
2016-05-11  7:45   ` Alexander Gordeev
2016-05-11  7:45     ` Alexander Gordeev
2016-05-11  8:50     ` Christoph Hellwig [this message]
2016-05-11  8:50       ` Christoph Hellwig
2016-05-11  9:44       ` Alexander Gordeev
2016-05-11  9:44         ` Alexander Gordeev
2016-05-12  7:35         ` Christoph Hellwig
2016-05-12  7:35           ` Christoph Hellwig
2016-05-12  9:44           ` Alexander Gordeev
2016-05-12  9:44             ` Alexander Gordeev
2016-05-12 11:03             ` Christoph Hellwig
2016-05-12 11:03               ` Christoph Hellwig
2016-05-12 12:11               ` Alexander Gordeev
2016-05-12 12:11                 ` Alexander Gordeev
2016-05-12 12:19                 ` Christoph Hellwig
2016-05-12 12:19                   ` Christoph Hellwig
2016-05-12 14:29                   ` Christoph Hellwig
2016-05-12 14:29                     ` Christoph Hellwig
2016-05-13  8:29                     ` Alexander Gordeev
2016-05-13  8:29                       ` Alexander Gordeev
2016-06-11  1:14                       ` Bjorn Helgaas
2016-06-11  1:14                         ` Bjorn Helgaas
2016-06-13 15:15                         ` Christoph Hellwig
2016-06-13 15:15                           ` Christoph Hellwig
2016-06-21 14:33                         ` Christoph Hellwig
2016-06-21 14:33                           ` Christoph Hellwig
2016-05-12 11:04   ` Alexander Gordeev
2016-05-12 11:04     ` Alexander Gordeev
2016-05-12 11:04     ` Christoph Hellwig
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-05 14:04   ` Christoph Hellwig
2016-05-10 15:27   ` Keith Busch
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=20160511085049.GA20279@lst.de \
    --to=hch@lst.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.