linux-kernel - replace pci_enable_msi_{exact_range} with pci_alloc_irq

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1473600688-24043-1-git-send-email-hch@lst.de>
Date:   Sun, 11 Sep 2016 15:31:22 +0200
From:   Christoph Hellwig <hch@....de>
To:     hans.verkuil@...co.com, brking@...ibm.com,
        haver@...ux.vnet.ibm.com, ching2048@...ca.com.tw, axboe@...com,
        alex.williamson@...hat.com
Cc:     kvm@...r.kernel.org, linux-scsi@...r.kernel.org,
        linux-block@...r.kernel.org, linux-media@...r.kernel.org,
        linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: replace pci_enable_msi_{exact_range} with pci_alloc_irq_vectors

Hi all,

this series switch the remaining users of pci_enable_msi_{exact_range}
(accounting for ahci and nvme being done through other channels) to
use the pci_alloc_irq_vectors helper instead and thus simplify the
interrupt code in those drivers a lot.  I decided to post it as a
series to everyone involved and linux-pci so that we can get a bit of
cross-review given that I have none of the involved hardware myself.