Re: [PATCH 5/7] dma-direct: handle DMA_ATTR_NON_CONSISTENT in common code

2019-06-25 Thread Christoph Hellwig
On Tue, Jun 25, 2019 at 02:23:45PM +0200, Helge Deller wrote: > On 14.06.19 16:44, Christoph Hellwig wrote: > > Only call into arch_dma_alloc if we require an uncached mapping, > > and remove the parisc code manually doing normal cached > > DMA_ATTR_NON_CONSISTENT allocations. > > > > Signed-off-by

Re: [PATCH 5/7] dma-direct: handle DMA_ATTR_NON_CONSISTENT in common code

2019-06-25 Thread Helge Deller
On 14.06.19 16:44, Christoph Hellwig wrote: > Only call into arch_dma_alloc if we require an uncached mapping, > and remove the parisc code manually doing normal cached > DMA_ATTR_NON_CONSISTENT allocations. > > Signed-off-by: Christoph Hellwig Acked-by: Helge Deller # parisc Boot-tested 32-bit

Re: [PATCH 5/7] dma-direct: handle DMA_ATTR_NON_CONSISTENT in common code

2019-06-24 Thread Christoph Hellwig
On Sun, Jun 16, 2019 at 06:08:40PM +0800, Hillf Danton wrote: > Literally, any cpu (call it cpuW) other than pcx12 and pcx1 will no longer do > dma alloc for any device with this patch applied. Yes. And that is not a chance from the previous code, where only pcx1 and pcx12 could do coherent alloc

[PATCH 5/7] dma-direct: handle DMA_ATTR_NON_CONSISTENT in common code

2019-06-14 Thread Christoph Hellwig
Only call into arch_dma_alloc if we require an uncached mapping, and remove the parisc code manually doing normal cached DMA_ATTR_NON_CONSISTENT allocations. Signed-off-by: Christoph Hellwig --- arch/parisc/kernel/pci-dma.c | 48 ++-- kernel/dma/direct.c