[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bb32d5a6-2b34-4524-e171-3e9f5f4d3a94@arm.com>
Date: Tue, 6 Jul 2021 16:39:11 +0100
From: Robin Murphy <robin.murphy@....com>
To: Christoph Hellwig <hch@....de>
Cc: Will Deacon <will@...nel.org>, heikki.krogerus@...ux.intel.com,
thomas.hellstrom@...ux.intel.com, peterz@...radead.org,
benh@...nel.crashing.org, joonas.lahtinen@...ux.intel.com,
dri-devel@...ts.freedesktop.org, chris@...is-wilson.co.uk,
grant.likely@....com, paulus@...ba.org,
Frank Rowand <frowand.list@...il.com>, mingo@...nel.org,
Stefano Stabellini <sstabellini@...nel.org>,
Saravana Kannan <saravanak@...gle.com>, mpe@...erman.id.au,
"Rafael J . Wysocki" <rafael.j.wysocki@...el.com>,
Bartosz Golaszewski <bgolaszewski@...libre.com>,
bskeggs@...hat.com, linux-pci@...r.kernel.org,
xen-devel@...ts.xenproject.org,
Thierry Reding <treding@...dia.com>,
intel-gfx@...ts.freedesktop.org, matthew.auld@...el.com,
linux-devicetree <devicetree@...r.kernel.org>,
Jianxiong Gao <jxgao@...gle.com>,
Daniel Vetter <daniel@...ll.ch>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
maarten.lankhorst@...ux.intel.com, airlied@...ux.ie,
Dan Williams <dan.j.williams@...el.com>,
linuxppc-dev@...ts.ozlabs.org, jani.nikula@...ux.intel.com,
Nathan Chancellor <nathan@...nel.org>,
Rob Herring <robh+dt@...nel.org>, rodrigo.vivi@...el.com,
Bjorn Helgaas <bhelgaas@...gle.com>,
Claire Chang <tientzu@...omium.org>,
boris.ostrovsky@...cle.com,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
jgross@...e.com, Nicolas Boichat <drinkcat@...omium.org>,
Greg KH <gregkh@...uxfoundation.org>,
Randy Dunlap <rdunlap@...radead.org>,
Qian Cai <quic_qiancai@...cinc.com>,
lkml <linux-kernel@...r.kernel.org>,
"list@....net:IOMMU DRIVERS" <iommu@...ts.linux-foundation.org>,
Jim Quinlan <james.quinlan@...adcom.com>, xypron.glpk@....de,
Tom Lendacky <thomas.lendacky@....com>, bauerman@...ux.ibm.com
Subject: Re: [PATCH v15 06/12] swiotlb: Use is_swiotlb_force_bounce for
swiotlb data bouncing
On 2021-07-06 15:05, Christoph Hellwig wrote:
> On Tue, Jul 06, 2021 at 03:01:04PM +0100, Robin Murphy wrote:
>> FWIW I was pondering the question of whether to do something along those
>> lines or just scrap the default assignment entirely, so since I hadn't got
>> round to saying that I've gone ahead and hacked up the alternative
>> (similarly untested) for comparison :)
>>
>> TBH I'm still not sure which one I prefer...
>
> Claire did implement something like your suggestion originally, but
> I don't really like it as it doesn't scale for adding multiple global
> pools, e.g. for the 64-bit addressable one for the various encrypted
> secure guest schemes.
Ah yes, that had slipped my mind, and it's a fair point indeed. Since
we're not concerned with a minimal fix for backports anyway I'm more
than happy to focus on Will's approach. Another thing is that that looks
to take us a quiet step closer to the possibility of dynamically
resizing a SWIOTLB pool, which is something that some of the hypervisor
protection schemes looking to build on top of this series may want to
explore at some point.
Robin.
Powered by blists - more mailing lists