[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <74c9662fca5a4d5896220a64aa9ad3ec@AcuMS.aculab.com>
Date: Wed, 14 Oct 2020 15:03:31 +0000
From: David Laight <David.Laight@...LAB.COM>
To: 'Tomasz Figa' <tfiga@...omium.org>, Christoph Hellwig <hch@....de>
CC: Mauro Carvalho Chehab <mchehab@...nel.org>,
Marek Szyprowski <m.szyprowski@...sung.com>,
"list@....net:IOMMU DRIVERS <iommu@...ts.linux-foundation.org>, Joerg
Roedel <joro@...tes.org>," <iommu@...ts.linux-foundation.org>,
Robin Murphy <robin.murphy@....com>,
Linux Doc Mailing List <linux-doc@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Media Mailing List <linux-media@...r.kernel.org>,
"ribalda@...omium.org" <ribalda@...omium.org>
Subject: RE: [PATCH 8/8] WIP: add a dma_alloc_contiguous API
> On Wed, Sep 30, 2020 at 6:09 PM Christoph Hellwig <hch@....de> wrote:
> >
> > Add a new API that returns a virtually non-contigous array of pages
> > and dma address. This API is only implemented for dma-iommu and will
> > not be implemented for non-iommu DMA API instances that have to allocate
> > contiguous memory. It is up to the caller to check if the API is
> > available.
Isn't there already a flag that is only implemented for ARM
systems with iommu that forces pages to actually be physically
contiguous?
So isn't this some kind of strange opposite?
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
Powered by blists - more mailing lists