WSL2-Linux-Kernel/kernel/dma
Nicolas Saenz Julienne d9765e41d8 dma-pool: do not allocate pool memory from CMA
There is no guarantee to CMA's placement, so allocating a zone specific
atomic pool from CMA might return memory from a completely different
memory zone. So stop using it.

Fixes: c84dc6e68a ("dma-pool: add additional coherent pools to map to gfp mask")
Reported-by: Jeremy Linton <jeremy.linton@arm.com>
Signed-off-by: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
Tested-by: Jeremy Linton <jeremy.linton@arm.com>
Acked-by: David Rientjes <rientjes@google.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
2020-07-14 15:46:32 +02:00
..
Kconfig dma-mapping: DMA_COHERENT_POOL should select GENERIC_ALLOCATOR 2020-06-23 14:13:58 +02:00
Makefile
coherent.c
contiguous.c
debug.c
direct.c dma-direct: provide function to check physical memory area validity 2020-07-14 15:42:24 +02:00
dummy.c
mapping.c dma-mapping: Add a new dma_need_sync API 2020-06-30 15:44:03 +02:00
pool.c dma-pool: do not allocate pool memory from CMA 2020-07-14 15:46:32 +02:00
remap.c dma-remap: align the size in dma_common_*_remap() 2020-06-23 14:14:41 +02:00
swiotlb.c
virt.c