All of lore.kernel.org
 help / color / mirror / Atom feed
From: helgaas@kernel.org (Bjorn Helgaas)
Subject: [PATCH 1/2] PCI: Provide sensible irq vector alloc/free routines
Date: Mon, 16 May 2016 14:39:29 -0500	[thread overview]
Message-ID: <20160516193929.GA20759@localhost> (raw)
In-Reply-To: <20160509224631.GB18501@localhost>

On Mon, May 09, 2016@05:46:31PM -0500, Bjorn Helgaas wrote:
> On Thu, May 05, 2016@04:04:55PM +0200, Christoph Hellwig wrote:
> > Add a new pci_alloc_irq_vectors helper that allocates MSI-X or multi-MSI
> > vectors for PCI device while isolating the driver from the arcane details.
> > 
> > This include handling both MSI-X, MSI and legacy interrupt fallbacks
> > transparently, automatic capping to the available vectors as well as storing
> > the information needed for request_irq in the PCI device itself so that
> > a lot of boiler plate code in the driver can be removed.
> > 
> > In the future this will also allow us to automatically set up spreading
> > for interrupt vectors without having to duplicate it in all the drivers.
> > 
> > Signed-off-by: Christoph Hellwig <hch at lst.de>
> 
> Thanks, I applied this to pci/msi for v4.7.

Given the subsequent discussion, it seems a little premature to merge
this for v4.7, so I'm dropping this for now.

Bjorn

WARNING: multiple messages have this Message-ID (diff)
From: Bjorn Helgaas <helgaas@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: agordeev@redhat.com, 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: Mon, 16 May 2016 14:39:29 -0500	[thread overview]
Message-ID: <20160516193929.GA20759@localhost> (raw)
In-Reply-To: <20160509224631.GB18501@localhost>

On Mon, May 09, 2016 at 05:46:31PM -0500, Bjorn Helgaas wrote:
> On Thu, May 05, 2016 at 04:04:55PM +0200, Christoph Hellwig wrote:
> > Add a new pci_alloc_irq_vectors helper that allocates MSI-X or multi-MSI
> > vectors for PCI device while isolating the driver from the arcane details.
> > 
> > This include handling both MSI-X, MSI and legacy interrupt fallbacks
> > transparently, automatic capping to the available vectors as well as storing
> > the information needed for request_irq in the PCI device itself so that
> > a lot of boiler plate code in the driver can be removed.
> > 
> > In the future this will also allow us to automatically set up spreading
> > for interrupt vectors without having to duplicate it in all the drivers.
> > 
> > Signed-off-by: Christoph Hellwig <hch@lst.de>
> 
> Thanks, I applied this to pci/msi for v4.7.

Given the subsequent discussion, it seems a little premature to merge
this for v4.7, so I'm dropping this for now.

Bjorn

  parent reply	other threads:[~2016-05-16 19:39 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 [this message]
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
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=20160516193929.GA20759@localhost \
    --to=helgaas@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 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.