All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Christoph Hellwig <hch@lst.de>
Cc: hans.verkuil@cisco.com, brking@us.ibm.com,
	haver@linux.vnet.ibm.com, ching2048@areca.com.tw, axboe@fb.com,
	alex.williamson@redhat.com, kvm@vger.kernel.org,
	linux-scsi@vger.kernel.org, linux-block@vger.kernel.org,
	linux-media@vger.kernel.org, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/6] ipr: use pci_irq_allocate_vectors
Date: Mon, 19 Sep 2016 16:44:40 -0400	[thread overview]
Message-ID: <yq1wpi78vrb.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <1473600688-24043-3-git-send-email-hch@lst.de> (Christoph Hellwig's message of "Sun, 11 Sep 2016 15:31:24 +0200")

>>>>> "Christoph" == Christoph Hellwig <hch@lst.de> writes:

Christoph> Switch the ipr driver to use pci_alloc_irq_vectors.  We need
Christoph> to two calls to pci_alloc_irq_vectors as ipr only supports
Christoph> multiple MSI-X vectors, but not multiple MSI vectors.

Christoph> Otherwise this cleans up a lot of cruft and allows to use a
Christoph> common request_irq loop for irq types, which happens to only
Christoph> iterate over a single line in the non MSI-X case.

Brian, Gabriel: Please test and review. Thanks!

-- 
Martin K. Petersen	Oracle Linux Engineering

  reply	other threads:[~2016-09-19 20:44 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-11 13:31 replace pci_enable_msi_{exact_range} with pci_alloc_irq_vectors Christoph Hellwig
2016-09-11 13:31 ` [PATCH 1/6] arcmsr: use pci_alloc_irq_vectors Christoph Hellwig
2016-09-19 20:45   ` Martin K. Petersen
2016-10-11 20:16   ` Martin K. Petersen
2016-09-11 13:31 ` [PATCH 2/6] ipr: use pci_irq_allocate_vectors Christoph Hellwig
2016-09-19 20:44   ` Martin K. Petersen [this message]
2016-09-29 14:01   ` Brian King
2016-09-29 15:32     ` Christoph Hellwig
2016-10-11 20:18   ` Martin K. Petersen
2016-09-11 13:31 ` [PATCH 3/6] skd: use pci_alloc_irq_vectors Christoph Hellwig
2016-09-29 18:44   ` Christoph Hellwig
2016-09-11 13:31 ` [PATCH 4/6] vfio_pci: use pci_irq_allocate_vectors Christoph Hellwig
2016-09-29 18:42   ` Christoph Hellwig
2016-09-29 19:21   ` Alex Williamson
2016-09-29 19:24     ` Christoph Hellwig
2016-09-29 19:27       ` Alex Williamson
2016-09-11 13:31 ` [PATCH 5/6] genwqe: " Christoph Hellwig
2016-09-29 18:28   ` Gabriel Krisman Bertazi
2016-09-29 18:37     ` Christoph Hellwig
2016-09-29 18:45       ` Gabriel Krisman Bertazi
2016-09-29 18:48         ` Christoph Hellwig
2016-09-29 18:51           ` Gabriel Krisman Bertazi
2016-09-11 13:31 ` [PATCH 6/6] media/cobalt: " Christoph Hellwig
2016-09-16  8:01   ` Hans Verkuil
2016-09-16  8:31     ` Christoph Hellwig
2016-12-14 10:29     ` Christoph Hellwig
2016-12-14 10:37       ` Hans Verkuil
2016-12-14 10:47         ` Christoph Hellwig
2016-12-14 10:52           ` Hans Verkuil

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=yq1wpi78vrb.fsf@sermon.lab.mkp.net \
    --to=martin.petersen@oracle.com \
    --cc=alex.williamson@redhat.com \
    --cc=axboe@fb.com \
    --cc=brking@us.ibm.com \
    --cc=ching2048@areca.com.tw \
    --cc=hans.verkuil@cisco.com \
    --cc=haver@linux.vnet.ibm.com \
    --cc=hch@lst.de \
    --cc=kvm@vger.kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-scsi@vger.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.