Hi Dave,
You'll get piles of those, and you get to rewrite the (x86) dma
implementation to fix them.
There's two parts of the problem:
- We hang onto dma mappings forever, and we don't enforce any
ownership. Actually we can't since our userspace _wants_ to access
some memory ranges while the gpu
WARNING: CPU: 1 PID: 24000 at lib/dma-debug.c:593
debug_dma_assert_idle+0x1a4/0x220()
i915 :00:02.0: DMA-API: cpu touching an active dma mapped cacheline
[cln=0x04401d40]
Modules linked in: ccm ip6t_rpfilter ip6t_REJECT xt_conntrack ebtable_nat
ebtable_broute bridge stp llc ebtable_f
2 matches
Mail list logo