NV50/GF100 behind constrained hierarchies
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest4 patches 2 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | drm/nouveau/bar/nv50: check bar1 vmm return valuedrivers/ | +2 | 0 replies | |
| 2/4 | drm/nouveau/bar/nv50: ensure BAR is mappeddrivers/ | +9 | 0 replies | |
| 3/4 | drm/nouveau/bar/gf100: ensure BAR is mappeddrivers/ | +2 | 0 replies | |
| 4/4 | drm/nouveau/mmu: qualify vmm during dtordrivers/ | +1 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/4] NV50/GF100 behind constrained hierarchies
Hi Ben,
I've been working with an mmio-constrained pci hierarchy intended almost solely for nvme devices and switches. Binding nouveau to an NV50-based gpu results in a kernel panic as the device cannot be fully mapped.
I've made modifications in nv50 and vmm to unbind the driver from this hierarchy, and modified gf100 assuming it will have the same issue.
1/4 also includes a fix where nv50 doesn't look like it checks the return value for nvkm_vmm_new for bar1. I don't know if this was intentional (eg, it could work without it).
I'm wholly unfamiliar with linux graphics drivers so let me know if there's a better place for this.
Jon Derrick (4):
drm/nouveau/bar/nv50: check bar1 vmm return value drm/nouveau/bar/nv50: ensure BAR is mapped drm/nouveau/bar/gf100: ensure BAR is mapped drm/nouveau/mmu: qualify vmm during dtor
drivers/gpu/drm/nouveau/nvkm/subdev/bar/gf100.c | 2 ++ drivers/gpu/drm/nouveau/nvkm/subdev/bar/nv50.c | 14 +++++++++++--- drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmm.c | 2 +- 3 files changed, 14 insertions(+), 4 deletions(-)
Signature · 6 lines
2.14.4 _______________________________________________ Nouveau mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/nouveau