[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <063D6719AE5E284EB5DD2968C1650D6DD0088B73@AcuExch.aculab.com>
Date: Tue, 3 Oct 2017 16:02:10 +0000
From: David Laight <David.Laight@...LAB.COM>
To: 'Christoph Hellwig' <hch@....de>,
"iommu@...ts.linux-foundation.org" <iommu@...ts.linux-foundation.org>
CC: Chris Zankel <chris@...kel.net>, Michal Simek <monstr@...str.eu>,
"linux-ia64@...r.kernel.org" <linux-ia64@...r.kernel.org>,
"linux-mips@...ux-mips.org" <linux-mips@...ux-mips.org>,
"linux-sh@...r.kernel.org" <linux-sh@...r.kernel.org>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
"linux-xtensa@...ux-xtensa.org" <linux-xtensa@...ux-xtensa.org>,
"x86@...nel.org" <x86@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
David Howells <dhowells@...hat.com>,
"Max Filippov" <jcmvbkbc@...il.com>,
Guan Xuetao <gxt@...c.pku.edu.cn>,
"Robin Murphy" <robin.murphy@....com>,
Marek Szyprowski <m.szyprowski@...sung.com>
Subject: RE: [PATCH 02/11] x86: make dma_cache_sync a no-op
From: Christoph Hellwig
> Sent: 03 October 2017 11:43
> x86 does not implement DMA_ATTR_NON_CONSISTENT allocations, so it doesn't
> make any sense to do any work in dma_cache_sync given that it must be a
> no-op when dma_alloc_attrs returns coherent memory.
I believe it is just about possible to require an explicit
write flush on x86.
ISTR this can happen with something like write combining.
Whether this can actually happen is the kernel is another matter.
David
Powered by blists - more mailing lists