Marek Marczykowski-Górecki 2c269f42d0 xen-pciback: Consider INTx disabled when MSI/MSI-X is enabled ... Linux enables MSI-X before disabling INTx, but keeps MSI-X masked until the table is filled. Then it disables INTx just before clearing MASKALL bit. Currently this approach is rejected by xen-pciback. According to the PCIe spec, device cannot use INTx when MSI/MSI-X is enabled (in other words: enabling MSI/MSI-X implicitly disables INTx). Change the logic to consider INTx disabled if MSI/MSI-X is enabled. This applies to three places: - checking currently enabled interrupts type, - transition to MSI/MSI-X - where INTx would be implicitly disabled, - clearing INTx disable bit - which can be allowed even if MSI/MSI-X is enabled, as device should consider INTx disabled anyway in that case Fixes: 5e29500eba ("xen-pciback: Allow setting PCI_MSIX_FLAGS_MASKALL too") Signed-off-by: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com> Acked-by: Juergen Gross <jgross@suse.com> Link: https://lore.kernel.org/r/20231016131348.1734721-1-marmarek@invisiblethingslab.com Signed-off-by: Juergen Gross <jgross@suse.com>		2023-10-16 15:20:31 +02:00
..
conf_space.c	xen-pciback: Consider INTx disabled when MSI/MSI-X is enabled	2023-10-16 15:20:31 +02:00
conf_space.h
conf_space_capability.c	xen-pciback: Consider INTx disabled when MSI/MSI-X is enabled	2023-10-16 15:20:31 +02:00
conf_space_header.c	xen-pciback: Consider INTx disabled when MSI/MSI-X is enabled	2023-10-16 15:20:31 +02:00
conf_space_quirks.c
conf_space_quirks.h
Makefile
passthrough.c
pci_stub.c
pciback.h
pciback_ops.c
vpci.c
xenbus.c