Fix breakage caused by the NTB multi-port patchset
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v3 Latest8 patches 3 repliesIn review
- v28 patches 8 repliesSuperseded
- v18 patches 21 repliesSuperseded
Changes in v3 from the cover letter
- Rebased on v5.0-rc1
- Modify Patch 2 to revert back to using the PCI struct device instead of the NTB struct device in DMA calls
- Collected Allen's Acks
- Collected Alexander's Tested-By
Patches in v3 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/8 | NTB: ntb_tool: reading the link file should not end in a NULL bytedrivers/ | +1 | 0 replies | |
| 2/8 | NTB: Revert the change to use the NTB device dev for DMA allocationsdrivers/ drivers/ drivers/ +3 more | +6 | 0 replies | |
| 3/8 | NTB: Fix the default port and peer numbers for legacy driversdrivers/ | +2 | 0 replies | |
| 4/8 | NTB: ntb_pingpong: Choose doorbells based on port numberdrivers/ | +6 | 0 replies | |
| 5/8 | NTB: perf: Don't require one more memory window than number of peersdrivers/ | +1 | 0 replies | |
| 6/8 | NTB: perf: Fix support for hardware that doesn't have port numbersdrivers/ | +10 | 0 replies | |
| 7/8 | NTB: perf: Fix race condition when run with ntb_testdrivers/ | +8 | 0 replies | |
| 8/8 | NTB: ntb_test: Fix bug when counting remote filestools/ | +1 | 0 replies |
Reviews trailers per patch
7 of 8 patches have a Reviewed-by or Acked-by.
| Patch | Allen Hubbe | Alexander Fomichev |
|---|---|---|
| 1/8 | A-b | T-b |
| 2/8 | T-b | |
| 3/8 | A-b | T-b |
| 4/8 | A-b | T-b |
| 5/8 | A-b | T-b |
| 6/8 | A-b | T-b |
| 7/8 | A-b | T-b |
| 8/8 | A-b | T-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH v3 0/8] Fix breakage caused by the NTB multi-port patchset
Hey,
I'm resending this because I've recently found out that the change we made to use the NTB struct device in DMA allocations is wrong and needs to be reverted. Turns out that, when running with an IOMMU, dma_alloc_coherent() will always fail if you pass it the NTB struct device. This is because the device has not been assigned an IOMMU group and the Intel IOMMU at least expect the devices to be on the PCI bus and be able to find a proper bus-dev-fn number through a struct pci device. Therefore, we must revert the change and I've changed patch 2 to do this and remove the no longer necessary DMA mask adjustments.
I'm not sure if we can get past the impass in getting this series merged:
I still maintain every patch in this series is necessary to fix a regression and there's no way to add port numbers to switchtec in the crosslink configuration so it can't be fixed in the other way that was suggested.
Logan
--
Changes since v2:
- Rebased on v5.0-rc1
- Modify Patch 2 to revert back to using the PCI struct device instead of the NTB struct device in DMA calls
- Collected Allen's Acks
- Collected Alexander's Tested-By
Changes since v1:
- Rebased onto ntb-next (there was a minor conflict in a recent change to the intel driver)
- Collected Dave's Ack
--
Logan Gunthorpe (8):
NTB: ntb_tool: reading the link file should not end in a NULL byte
NTB: Revert the change to use the NTB device dev for DMA allocations
NTB: Fix the default port and peer numbers for legacy drivers
NTB: ntb_pingpong: Choose doorbells based on port number
NTB: perf: Don't require one more memory window than number of peers
NTB: perf: Fix support for hardware that doesn't have port numbers
NTB: perf: Fix race condition when run with ntb_test
NTB: ntb_test: Fix bug when counting remote files
drivers/ntb/hw/amd/ntb_hw_amd.c | 4 ---- drivers/ntb/hw/idt/ntb_hw_idt.c | 6 ----- drivers/ntb/hw/intel/ntb_hw_gen1.c | 4 ---- drivers/ntb/ntb.c | 9 ++------ drivers/ntb/test/ntb_perf.c | 29 +++++++++++++++++++------ drivers/ntb/test/ntb_pingpong.c | 14 +++++------- drivers/ntb/test/ntb_tool.c | 9 ++++---- tools/testing/selftests/ntb/ntb_test.sh | 2 +- 8 files changed, 35 insertions(+), 42 deletions(-)
--
2.19.0