Rob Clark cd8c1e6c01 dma-debug: make things less spammy under memory pressure ...

[ Upstream commit e19f8fa6ce1ca9b8b934ba7d2e8f34c95abc6e60 ]

Limit the error msg to avoid flooding the console.  If you have a lot of
threads hitting this at once, they could have already gotten passed the
dma_debug_disabled() check before they get to the point of allocation
failure, resulting in quite a lot of this error message spamming the
log.  Use pr_err_once() to limit that.

Signed-off-by: Rob Clark <robdclark@chromium.org>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Sasha Levin <sashal@kernel.org>

2022-06-22 14:11:19 +02:00

..

coherent.c

dma-coherent: fix integer overflow in the reserved-memory dma allocation

2020-04-23 10:36:30 +02:00

contiguous.c

dma-direct: fix zone selection after an unaddressable CMA allocation

2019-08-21 07:14:10 +09:00

debug.c

dma-debug: make things less spammy under memory pressure

2022-06-22 14:11:19 +02:00

direct.c

dma-direct: avoid redundant memory sync for swiotlb

2022-04-20 09:19:39 +02:00

dummy.c

dma-mapping: factor out dummy DMA ops

2018-12-13 21:06:12 +01:00

Kconfig

dma-mapping: remove arch_dma_mmap_pgprot

2019-08-29 16:43:22 +02:00

Makefile

dma-mapping: improve selection of dma_declare_coherent availability

2019-02-20 07:26:35 -07:00

mapping.c

dma-mapping: Fix dma_pgprot() for unencrypted coherent pages

2020-04-17 10:50:01 +02:00

remap.c

dma-mapping: fix false positivse warnings in dma_common_free_remap()

2019-10-05 10:24:17 +02:00

swiotlb.c

Reinstate some of "swiotlb: rework "fix info leak with DMA_FROM_DEVICE""

2022-05-25 09:14:38 +02:00

virt.c

dma-mapping: zero memory returned from dma_alloc_*

2018-12-20 08:13:52 +01:00