[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1d06eda1-9961-d023-f5e7-fe87e768f067@arm.com>
Date: Mon, 2 Aug 2021 17:16:48 +0100
From: Robin Murphy <robin.murphy@....com>
To: John Garry <john.garry@...wei.com>, Will Deacon <will@...nel.org>
Cc: joro@...tes.org, baolu.lu@...ux.intel.com,
iommu@...ts.linux-foundation.org, linuxarm@...wei.com,
thierry.reding@...il.com, airlied@...ux.ie, daniel@...ll.ch,
jonathanh@...dia.com, sakari.ailus@...ux.intel.com,
bingbu.cao@...el.com, tian.shu.qiu@...el.com, mchehab@...nel.org,
gregkh@...uxfoundation.org, digetx@...il.com, mst@...hat.com,
jasowang@...hat.com, linux-kernel@...r.kernel.org,
chenxiang66@...ilicon.com
Subject: Re: [PATCH v4 5/6] iova: Add iova_len argument to init_iova_domain()
On 2021-08-02 17:06, John Garry wrote:
> On 02/08/2021 16:06, Will Deacon wrote:
>> On Wed, Jul 14, 2021 at 06:36:42PM +0800, John Garry wrote:
>>> Add max opt argument to init_iova_domain(), and use it to set the
>>> rcaches
>>> range.
>>>
>>> Also fix up all users to set this value (at 0, meaning use default).
>> Wrap that in init_iova_domain_defaults() to avoid the mysterious 0?
>
> Sure, I can do something like that. I actually did have separate along
> those lines in v3 before I decided to change it.
Y'know, at this point I'm now starting to seriously wonder whether
moving the rcaches into iommu_dma_cookie wouldn't make a whole lot of
things simpler... :/
Does that sound like crazy talk to you, or an idea worth entertaining?
Robin.
Powered by blists - more mailing lists