Thread (25 messages) 25 messages, 3 authors, 2016-07-12

Re: [PATCH 07/13] pci: Provide sensible irq vector alloc/free routines

From: Christoph Hellwig <hch@lst.de>
Date: 2016-07-12 09:13:07
Also in: linux-nvme, linux-pci, lkml

On Mon, Jul 11, 2016 at 12:43:41PM +0200, Alexander Gordeev wrote:
quoted
I diagreed - if we deprecated functions the only thing that should
be mentioned is a "don't use these". 
I will try to paraphrase myself. The new API deprecates pci_enable_msi*_range
functions, but I am not that sure about others. Certainly, pci_msi*_vec_count
and pci_enable_msi*_exact could have (and AFAIR do have) uses that can not be
covered by automatic initialization of pci_alloc_irq_vectors().
pci_enable_msi*_exact is the equivalent of pci_enable_msi*_range
with minvecs == maxvecs and treating any return value >= 0 as 0.

I've updated the documentation so that the old usage examples are kept
around, but now use pci_alloc_irq_vectors.  I've also added a more detaild
blurb on pci_msi*_vec_count - I think there is no need for them, but
if I'm proven wrong we'll have to add a pci_irq_vector_count that handles
all interrupt types later.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help