Fix DMA ops layering violations in vmwgfx v2
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest4 patches 3 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | drm/vmwgfx: remove CONFIG_X86 ifdefsdrivers/ | +0 | 0 replies | |
| 2/4 | drm/vmwgfx: remove CONFIG_INTEL_IOMMU ifdefs v2drivers/ | +4 | 3 replies | |
| 3/4 | drm/vmwgfx: fix the check when to use dma_alloc_coherentdrivers/ | +4 | 0 replies | |
| 4/4 | drm/vmwgfx: unwind spaghetti code in vmw_dma_select_modedrivers/ | +6 | 0 replies |
Reviews trailers per patch
1 of 4 patches has a Reviewed-by or Acked-by.
| Patch | Thomas Hellstrom |
|---|---|
| 1/4 | |
| 2/4 | R-b |
| 3/4 | |
| 4/4 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/4] Fix DMA ops layering violations in vmwgfx v2
This is a patch set from Christoph Hellwig. Patch 2 has been updated by me to not remove checks for TTM coherent pool presence. Ideally, we should query TTM for this instead and I'll have a patch set intended for 5.1 so that we can do that. But I don't want to introduce cross-module API additions outside of a merge window.
Original patch set description:
vmwgfx has been doing some odd checks based on DMA ops which rely on deep DMA mapping layer internals, and I think the changes in Linux 4.21 finally broke most of these implicit assumptions.
The real fix is in patch 3, but I think the others are important to make it clear what is actually going on.
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel