[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190605055021.GA15036@infradead.org>
Date: Tue, 4 Jun 2019 22:50:21 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Tom Murphy <tmurphy@...sta.com>
Cc: iommu@...ts.linux-foundation.org, Heiko Stuebner <heiko@...ech.de>,
Will Deacon <will.deacon@....com>,
David Brown <david.brown@...aro.org>,
Thierry Reding <thierry.reding@...il.com>,
linux-s390@...r.kernel.org, linux-samsung-soc@...r.kernel.org,
Krzysztof Kozlowski <krzk@...nel.org>,
Jonathan Hunter <jonathanh@...dia.com>,
linux-rockchip@...ts.infradead.org, Kukjin Kim <kgene@...nel.org>,
Gerald Schaefer <gerald.schaefer@...ibm.com>,
Andy Gross <andy.gross@...aro.org>,
linux-tegra@...r.kernel.org, linux-arm-msm@...r.kernel.org,
linux-mediatek@...ts.infradead.org,
Matthias Brugger <matthias.bgg@...il.com>,
linux-arm-kernel@...ts.infradead.org,
Robin Murphy <robin.murphy@....com>,
linux-kernel@...r.kernel.org, murphyt7@....ie,
David Woodhouse <dwmw2@...radead.org>
Subject: Re: [PATCH v3 1/4] iommu: Add gfp parameter to iommu_ops::map
On Mon, May 06, 2019 at 07:52:03PM +0100, Tom Murphy via iommu wrote:
> We can remove the mutex lock from amd_iommu_map and amd_iommu_unmap.
> iommu_map doesn’t lock while mapping and so no two calls should touch
> the same iova range. The AMD driver already handles the page table page
> allocations without locks so we can safely remove the locks.
Btw, this really should be a separate patch.
Powered by blists - more mailing lists