x86: Fix racy accesses to MSI-X Control register
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 8 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | x86/msi: consistently handle BAR mapping failures in MSI-X setupxen/ | +1 | 1 reply | |
| 2/3 | x86/msi: remove return value from msi_set_mask_bit()xen/ | +9 | 3 replies | |
| 3/3 | x86/pci: Fix racy accesses to MSI-X Control registerxen/ xen/ xen/ | +114 | 4 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/3] x86: Fix racy accesses to MSI-X Control register
The main patch in this series is 3/3 with some preparatory patches to simplify the implementation. To summarize:
Concurrent access the the MSI-X control register are not serialized with a suitable lock. For example, in msix_capability_init() access use the pcidevs_lock() but some calls to msi_set_mask_bit() use the interrupt descriptor lock.
This can lead to MSI-X being incorrectly disabled and subsequent failures due to msix_memory_decoded() calls that check for MSI-X being enabled.
David