Keith Busch cb9e0e5006 nvme-pci: use blk-mq mapping for unmanaged irqs ... If a device is providing a single IRQ vector, the IO queue will share that vector with the admin queue. This is an unmanaged vector, so does not have a valid PCI IRQ affinity. Avoid trying to extract a managed affinity in this case and let blk-mq set up the cpu:queue mapping instead. Otherwise we'd hit the following warning when the device is using MSI: WARNING: CPU: 4 PID: 7 at drivers/pci/msi.c:1272 pci_irq_get_affinity+0x66/0x80 Modules linked in: nvme nvme_core serio_raw CPU: 4 PID: 7 Comm: kworker/u16:0 Tainted: G W 5.2.0-rc1+ #494 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org 04/01/2014 Workqueue: nvme-reset-wq nvme_reset_work [nvme] RIP: 0010:pci_irq_get_affinity+0x66/0x80 Code: 0b 31 c0 c3 83 e2 10 48 c7 c0 b0 83 35 91 74 2a 48 8b 87 d8 03 00 00 48 85 c0 74 0e 48 8b 50 30 48 85 d2 74 05 39 70 14 77 05 <0f> 0b 31 c0 c3 48 63 f6 48 8d 04 76 48 8d 04 c2 f3 c3 48 8b 40 30 RSP: 0000:ffffb5abc01d3cc8 EFLAGS: 00010246 RAX: ffff9536786a39c0 RBX: 0000000000000000 RCX: 0000000000000080 RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff9536781ed000 RBP: ffff95367346a008 R08: ffff95367d43f080 R09: ffff953678c07800 R10: ffff953678164800 R11: 0000000000000000 R12: 0000000000000000 R13: ffff9536781ed000 R14: 00000000ffffffff R15: ffff95367346a008 FS: 0000000000000000(0000) GS:ffff95367d400000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fdf814a3ff0 CR3: 000000001a20f000 CR4: 00000000000006e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: blk_mq_pci_map_queues+0x37/0xd0 nvme_pci_map_queues+0x80/0xb0 [nvme] blk_mq_alloc_tag_set+0x133/0x2f0 nvme_reset_work+0x105d/0x1590 [nvme] process_one_work+0x291/0x530 worker_thread+0x218/0x3d0 ? process_one_work+0x530/0x530 kthread+0x111/0x130 ? kthread_park+0x90/0x90 ret_from_fork+0x1f/0x30 ---[ end trace 74587339d93c83c0 ]--- Fixes: 22b5560195 ("nvme-pci: Separate IO and admin queue IRQ vectors") Reported-by: Iván Chavero <ichavero@chavero.com.mx> Reviewed-by: Ming Lei <ming.lei@redhat.com> Signed-off-by: Keith Busch <keith.busch@intel.com>		2019-05-22 10:11:36 -06:00
..
Kconfig	nvme-tcp: add NVMe over TCP host driver	2018-12-13 09:58:58 +01:00
Makefile	nvme-tcp: add NVMe over TCP host driver	2018-12-13 09:58:58 +01:00
core.c	nvme: copy MTFA field from identify controller	2019-05-21 09:01:37 -06:00
fabrics.c	nvme-fabrics: remove unused argument	2019-05-14 17:19:43 +02:00
fabrics.h	nvme-fabrics: convert to SPDX identifiers	2019-02-20 07:22:13 -07:00
fault_inject.c	nvme: convert to SPDX identifiers	2019-02-20 07:22:28 -07:00
fc.c	for-5.2/block-post-20190516	2019-05-16 19:08:15 -07:00
lightnvm.c	lightnvm: Inherit mdts from the parent nvme device	2019-05-06 10:19:17 -06:00
multipath.c	nvme-multipath: avoid crash on invalid subsystem cntlid enumeration	2019-05-13 16:00:03 +02:00
nvme.h	nvme-pci: Sync queues on reset	2019-05-17 11:04:34 -06:00
pci.c	nvme-pci: use blk-mq mapping for unmanaged irqs	2019-05-22 10:11:36 -06:00
rdma.c	nvme-rdma: remove redundant reference between ib_device and tagset	2019-05-13 16:00:03 +02:00
tcp.c	nvme-tcp: fix possible null deref on a timed out io queue connect	2019-05-01 09:17:15 -04:00
trace.c	nvme: add get-feature to admin cmds tracer	2019-03-13 12:05:39 -06:00
trace.h	nvme: trace all async notice events	2019-05-14 17:19:47 +02:00