Re: [rfc 5/6] dma-direct: atomic allocations must come from unencrypted pools

2020-03-10 Thread Christoph Hellwig
On Fri, Mar 06, 2020 at 04:36:07PM -0800, David Rientjes wrote: > As a preliminary change to this series, I could move the atomic pools and > coherent_pool command line to a new kernel/dma/atomic_pools.c file with a > new CONFIG_DMA_ATOMIC_POOLS that would get "select"ed by CONFIG_DMA_REMAP > an

Re: [rfc 5/6] dma-direct: atomic allocations must come from unencrypted pools

2020-03-06 Thread David Rientjes via iommu
On Thu, 5 Mar 2020, Christoph Hellwig wrote: > On Sun, Mar 01, 2020 at 04:05:23PM -0800, David Rientjes wrote: > > When AMD memory encryption is enabled, all non-blocking DMA allocations > > must originate from the atomic pools depending on the device and the gfp > > mask of the allocation. > > >

Re: [rfc 5/6] dma-direct: atomic allocations must come from unencrypted pools

2020-03-05 Thread Christoph Hellwig
On Sun, Mar 01, 2020 at 04:05:23PM -0800, David Rientjes wrote: > When AMD memory encryption is enabled, all non-blocking DMA allocations > must originate from the atomic pools depending on the device and the gfp > mask of the allocation. > > Keep all memory in these pools unencrypted. > > Signed

[rfc 5/6] dma-direct: atomic allocations must come from unencrypted pools

2020-03-01 Thread David Rientjes via iommu
When AMD memory encryption is enabled, all non-blocking DMA allocations must originate from the atomic pools depending on the device and the gfp mask of the allocation. Keep all memory in these pools unencrypted. Signed-off-by: David Rientjes --- arch/x86/Kconfig| 1 + kernel/dma/direct.c |