Re: [PATCH 2/2] iommu: Introduce Interface for IOMMU TLB Flushing

Hi Will, On Fri, Sep 01, 2017 at 06:20:45PM +0100, Will Deacon wrote: > On Wed, Aug 23, 2017 at 03:50:04PM +0200, Joerg Roedel wrote: > > +EXPORT_SYMBOL_GPL(iommu_unmap_fast); > > Really minor nit, but I think that iommu_unmap_nosync is a more descriptive > name (who wouldn't want to use the

[PATCH] mm/mmu_notifier: avoid double notification when it is useless

From: Jérôme Glisse (Note that this is 4.15 material or 4.14 if people are extra confident. I am posting now to get people to test. To that effect maybe it would be a good idea to have that patch sit in linux-next for a while for testing. Other motivation is that the

Re: [PATCH 2/2] iommu: Introduce Interface for IOMMU TLB Flushing

Hi Joerg, On Wed, Aug 23, 2017 at 03:50:04PM +0200, Joerg Roedel wrote: > From: Joerg Roedel > > With the current IOMMU-API the hardware TLBs have to be > flushed in every iommu_ops->unmap() call-back. > > For unmapping large amounts of address space, like it > happens when a

Re: [PATCH 2/2] iommu/omap: Add support to program multiple iommus

On 09/01/2017 11:33 AM, Joerg Roedel wrote: > Hi Suman, > On Fri, Sep 01, 2017 at 11:21:45AM -0500, Suman Anna wrote: >> It's primarily a question of whether each iommu platform device need to >> be represented as a unique iommu_device or not. If you still think that >> both these need to be

Re: [PATCH 2/2] iommu/omap: Add support to program multiple iommus

Hi Suman, On Fri, Sep 01, 2017 at 11:21:45AM -0500, Suman Anna wrote: > It's primarily a question of whether each iommu platform device need to > be represented as a unique iommu_device or not. If you still think that > both these need to be presented to iommu core as one device, I would > have to

Re: [PATCH 2/2] iommu/omap: Add support to program multiple iommus

Hi Joerg, On 09/01/2017 05:01 AM, Joerg Roedel wrote: > Hi Suman, > > On Thu, Aug 31, 2017 at 08:14:02AM -0500, Suman Anna wrote: >> The OMAP IOMMU driver has been enhanced to support allowing >> multiple IOMMUs to be programmed by a single client user. This >> support is being added mainly to

Re: [PATCH 00/13] mmu_notifier kill invalidate_page callback

On Wed, Aug 30, 2017, at 10:57 AM, Adam Borowski wrote: > On Tue, Aug 29, 2017 at 08:56:15PM -0400, Jerome Glisse wrote: > > I will wait for people to test and for result of my own test before > > reposting if need be, otherwise i will post as separate patch. > > > > > But from a _very_ quick

Re: [PATCH 00/13] mmu_notifier kill invalidate_page callback

taskboxtes...@gmail.com liked your message with Boxer for Android. On Sep 1, 2017 10:48 AM, Jeff Cook wrote: On Wed, Aug 30, 2017, at 10:57 AM, Adam Borowski wrote: > On Tue, Aug 29, 2017 at 08:56:15PM -0400, Jerome Glisse wrote: > > I will wait for people to test and for

Re: [PATCH 2/2] iommu/omap: Add support to program multiple iommus

Hi Suman, On Thu, Aug 31, 2017 at 08:14:02AM -0500, Suman Anna wrote: > The OMAP IOMMU driver has been enhanced to support allowing > multiple IOMMUs to be programmed by a single client user. This > support is being added mainly to handle the DSP subsystems on > the DRA7xx SoCs, which have two

Re: [PATCH] MAINTAINERS: use the iommu list for the dma-mapping subsystem

On Fri, Sep 01, 2017 at 10:48:50AM +0100, Robin Murphy wrote: > On 01/09/17 08:56, Marek Szyprowski wrote: > > Hi Christoph, > > > > On 2017-09-01 09:50, Christoph Hellwig wrote: > >> Any comments? I'd like to add this to the 4.14 pull request. > >> > >> On Sat, Aug 26, 2017 at 11:27:34AM +0200,

Re: [PATCH] MAINTAINERS: use the iommu list for the dma-mapping subsystem

On 01/09/17 08:56, Marek Szyprowski wrote: > Hi Christoph, > > On 2017-09-01 09:50, Christoph Hellwig wrote: >> Any comments? I'd like to add this to the 4.14 pull request. >> >> On Sat, Aug 26, 2017 at 11:27:34AM +0200, Christoph Hellwig wrote: >>> Maintaining a subsystem with linux-kernel as

Re: [PATCH] iommu/dma: limit the IOVA allocated to dma-ranges region

On 01/09/17 10:26, Joerg Roedel wrote: > Adding Robin for review. > > On Thu, Aug 31, 2017 at 03:08:21PM -0700, Krishna Reddy wrote: >> Limit the IOVA allocated to dma-ranges specified for the device. >> This is necessary to ensure that IOVA allocated is addressable >> by device. Why? IOVA

Re: [PATCH v2] iommu/vt-d: Don't be too aggressive when clearing one context entry

On Thu, Aug 31, 2017 at 10:58:11AM +0200, Filippo Sironi wrote: > Previously, we were invalidating context cache and IOTLB globally when > clearing one context entry. This is a tad too aggressive. > Invalidate the context cache and IOTLB for the interested device only. > > Signed-off-by: Filippo

Re: [PATCH] iommu/dma: limit the IOVA allocated to dma-ranges region

Adding Robin for review. On Thu, Aug 31, 2017 at 03:08:21PM -0700, Krishna Reddy wrote: > Limit the IOVA allocated to dma-ranges specified for the device. > This is necessary to ensure that IOVA allocated is addressable > by device. > > Signed-off-by: Krishna Reddy > --- >

Re: [PATCH v6 3/3] iommu/arm-smmu-v3:Enable ACPI based HiSilicon erratum 161010801

On 10/08/2017 18:27, Will Deacon wrote: On Wed, Aug 09, 2017 at 11:07:15AM +0100, Shameer Kolothum wrote: The HiSilicon erratum 161010801 describes the limitation of HiSilicon platforms Hip06/Hip07 to support the SMMU mappings for MSI transactions. On these platforms GICv3 ITS translator is

Re: [PATCH] MAINTAINERS: use the iommu list for the dma-mapping subsystem

Hi Christoph, On 2017-09-01 09:50, Christoph Hellwig wrote: Any comments? I'd like to add this to the 4.14 pull request. On Sat, Aug 26, 2017 at 11:27:34AM +0200, Christoph Hellwig wrote: Maintaining a subsystem with linux-kernel as the main list is painful as it has way to much traffic. On

Re: [PATCH] MAINTAINERS: use the iommu list for the dma-mapping subsystem

Any comments? I'd like to add this to the 4.14 pull request. On Sat, Aug 26, 2017 at 11:27:34AM +0200, Christoph Hellwig wrote: > Maintaining a subsystem with linux-kernel as the main list is painful > as it has way to much traffic. On the other hand the dma-mapping > subsystem is small enough