Keith Busch a5229050b6 NVMe: Always use MSI/MSI-x interrupts ... Multiple users have reported device initialization failure due the driver not receiving legacy PCI interrupts. This is not unique to any particular controller, but has been observed on multiple platforms. There have been no issues reported or observed when with message signaled interrupts, so this patch attempts to use MSI-x during initialization, falling back to MSI. If that fails, legacy would become the default. The setup_io_queues error handling had to change as a result: the admin queue's msix_entry used to be initialized to the legacy IRQ. The case where nr_io_queues is 0 would fail request_irq when setting up the admin queue's interrupt since re-enabling MSI-x fails with 0 vectors, leaving the admin queue's msix_entry invalid. Instead, return success immediately. Reported-by: Tim Muhlemmer <muhlemmer@gmail.com> Reported-by: Jon Derrick <jonathan.derrick@intel.com> Signed-off-by: Keith Busch <keith.busch@intel.com> Signed-off-by: Jens Axboe <axboe@fb.com>		2016-04-14 14:04:50 -06:00
..
host	NVMe: Always use MSI/MSI-x interrupts	2016-04-14 14:04:50 -06:00
Kconfig	nvme: move to a new drivers/nvme/host directory	2015-10-09 10:40:37 -06:00
Makefile	nvme: move to a new drivers/nvme/host directory	2015-10-09 10:40:37 -06:00