David Rientjes 76a19940bd dma-direct: atomic allocations must come from atomic coherent pools ... When a device requires unencrypted memory and the context does not allow blocking, memory must be returned from the atomic coherent pools. This avoids the remap when CONFIG_DMA_DIRECT_REMAP is not enabled and the config only requires CONFIG_DMA_COHERENT_POOL. This will be used for CONFIG_AMD_MEM_ENCRYPT in a subsequent patch. Keep all memory in these pools unencrypted. When set_memory_decrypted() fails, this prohibits the memory from being added. If adding memory to the genpool fails, and set_memory_encrypted() subsequently fails, there is no alternative other than leaking the memory. Signed-off-by: David Rientjes <rientjes@google.com> Signed-off-by: Christoph Hellwig <hch@lst.de>		2020-04-25 13:17:05 +02:00
..
coherent.c
contiguous.c
debug.c	dma-debug: make __dma_entry_alloc_check_leak() static	2020-04-20 12:05:18 +02:00
direct.c	dma-direct: atomic allocations must come from atomic coherent pools	2020-04-25 13:17:05 +02:00
dummy.c
Kconfig	dma-remap: separate DMA atomic pools from direct remap code	2020-04-20 12:08:45 +02:00
Makefile	dma-remap: separate DMA atomic pools from direct remap code	2020-04-20 12:08:45 +02:00
mapping.c
pool.c	dma-direct: atomic allocations must come from atomic coherent pools	2020-04-25 13:17:05 +02:00
remap.c	dma-remap: separate DMA atomic pools from direct remap code	2020-04-20 12:08:45 +02:00
swiotlb.c
virt.c