All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-Philippe Brucker <jean-philippe@linaro.org>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: iommu@lists.linux-foundation.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-pci@vger.kernel.org,
	linux-mm@kvack.org, joro@8bytes.org, robh+dt@kernel.org,
	mark.rutland@arm.com, catalin.marinas@arm.com, will@kernel.org,
	robin.murphy@arm.com, kevin.tian@intel.com,
	baolu.lu@linux.intel.com, jacob.jun.pan@linux.intel.com,
	christian.koenig@amd.com, yi.l.liu@intel.com,
	zhangfei.gao@linaro.org,
	Jean-Philippe Brucker <jean-philippe.brucker@arm.com>
Subject: Re: [PATCH v4 07/26] arm64: mm: Pin down ASIDs for sharing mm with devices
Date: Wed, 4 Mar 2020 15:10:45 +0100	[thread overview]
Message-ID: <20200304141045.GD646000@myrica> (raw)
In-Reply-To: <20200227174351.00004d0d@Huawei.com>

On Thu, Feb 27, 2020 at 05:43:51PM +0000, Jonathan Cameron wrote:
> On Mon, 24 Feb 2020 19:23:42 +0100
> Jean-Philippe Brucker <jean-philippe@linaro.org> wrote:
> 
> > From: Jean-Philippe Brucker <jean-philippe.brucker@arm.com>
> > 
> > To enable address space sharing with the IOMMU, introduce mm_context_get()
> > and mm_context_put(), that pin down a context and ensure that it will keep
> > its ASID after a rollover. Export the symbols to let the modular SMMUv3
> > driver use them.
> > 
> > Pinning is necessary because a device constantly needs a valid ASID,
> > unlike tasks that only require one when running. Without pinning, we would
> > need to notify the IOMMU when we're about to use a new ASID for a task,
> > and it would get complicated when a new task is assigned a shared ASID.
> > Consider the following scenario with no ASID pinned:
> > 
> > 1. Task t1 is running on CPUx with shared ASID (gen=1, asid=1)
> > 2. Task t2 is scheduled on CPUx, gets ASID (1, 2)
> > 3. Task tn is scheduled on CPUy, a rollover occurs, tn gets ASID (2, 1)
> >    We would now have to immediately generate a new ASID for t1, notify
> >    the IOMMU, and finally enable task tn. We are holding the lock during
> >    all that time, since we can't afford having another CPU trigger a
> >    rollover. The IOMMU issues invalidation commands that can take tens of
> >    milliseconds.
> > 
> > It gets needlessly complicated. All we wanted to do was schedule task tn,
> > that has no business with the IOMMU. By letting the IOMMU pin tasks when
> > needed, we avoid stalling the slow path, and let the pinning fail when
> > we're out of shareable ASIDs.
> > 
> > After a rollover, the allocator expects at least one ASID to be available
> > in addition to the reserved ones (one per CPU). So (NR_ASIDS - NR_CPUS -
> > 1) is the maximum number of ASIDs that can be shared with the IOMMU.
> > 
> > Signed-off-by: Jean-Philippe Brucker <jean-philippe@linaro.org>
> A few more trivial points.

I'll fix those, thanks

Jean

WARNING: multiple messages have this Message-ID (diff)
From: Jean-Philippe Brucker <jean-philippe@linaro.org>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
	kevin.tian@intel.com,
	Jean-Philippe Brucker <jean-philippe.brucker@arm.com>,
	linux-pci@vger.kernel.org, robin.murphy@arm.com,
	linux-mm@kvack.org, iommu@lists.linux-foundation.org,
	robh+dt@kernel.org, catalin.marinas@arm.com,
	zhangfei.gao@linaro.org, will@kernel.org,
	christian.koenig@amd.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 07/26] arm64: mm: Pin down ASIDs for sharing mm with devices
Date: Wed, 4 Mar 2020 15:10:45 +0100	[thread overview]
Message-ID: <20200304141045.GD646000@myrica> (raw)
In-Reply-To: <20200227174351.00004d0d@Huawei.com>

On Thu, Feb 27, 2020 at 05:43:51PM +0000, Jonathan Cameron wrote:
> On Mon, 24 Feb 2020 19:23:42 +0100
> Jean-Philippe Brucker <jean-philippe@linaro.org> wrote:
> 
> > From: Jean-Philippe Brucker <jean-philippe.brucker@arm.com>
> > 
> > To enable address space sharing with the IOMMU, introduce mm_context_get()
> > and mm_context_put(), that pin down a context and ensure that it will keep
> > its ASID after a rollover. Export the symbols to let the modular SMMUv3
> > driver use them.
> > 
> > Pinning is necessary because a device constantly needs a valid ASID,
> > unlike tasks that only require one when running. Without pinning, we would
> > need to notify the IOMMU when we're about to use a new ASID for a task,
> > and it would get complicated when a new task is assigned a shared ASID.
> > Consider the following scenario with no ASID pinned:
> > 
> > 1. Task t1 is running on CPUx with shared ASID (gen=1, asid=1)
> > 2. Task t2 is scheduled on CPUx, gets ASID (1, 2)
> > 3. Task tn is scheduled on CPUy, a rollover occurs, tn gets ASID (2, 1)
> >    We would now have to immediately generate a new ASID for t1, notify
> >    the IOMMU, and finally enable task tn. We are holding the lock during
> >    all that time, since we can't afford having another CPU trigger a
> >    rollover. The IOMMU issues invalidation commands that can take tens of
> >    milliseconds.
> > 
> > It gets needlessly complicated. All we wanted to do was schedule task tn,
> > that has no business with the IOMMU. By letting the IOMMU pin tasks when
> > needed, we avoid stalling the slow path, and let the pinning fail when
> > we're out of shareable ASIDs.
> > 
> > After a rollover, the allocator expects at least one ASID to be available
> > in addition to the reserved ones (one per CPU). So (NR_ASIDS - NR_CPUS -
> > 1) is the maximum number of ASIDs that can be shared with the IOMMU.
> > 
> > Signed-off-by: Jean-Philippe Brucker <jean-philippe@linaro.org>
> A few more trivial points.

I'll fix those, thanks

Jean
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

WARNING: multiple messages have this Message-ID (diff)
From: Jean-Philippe Brucker <jean-philippe@linaro.org>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
	kevin.tian@intel.com, jacob.jun.pan@linux.intel.com,
	Jean-Philippe Brucker <jean-philippe.brucker@arm.com>,
	linux-pci@vger.kernel.org, joro@8bytes.org, robin.murphy@arm.com,
	linux-mm@kvack.org, iommu@lists.linux-foundation.org,
	robh+dt@kernel.org, yi.l.liu@intel.com, catalin.marinas@arm.com,
	zhangfei.gao@linaro.org, will@kernel.org,
	christian.koenig@amd.com, linux-arm-kernel@lists.infradead.org,
	baolu.lu@linux.intel.com
Subject: Re: [PATCH v4 07/26] arm64: mm: Pin down ASIDs for sharing mm with devices
Date: Wed, 4 Mar 2020 15:10:45 +0100	[thread overview]
Message-ID: <20200304141045.GD646000@myrica> (raw)
In-Reply-To: <20200227174351.00004d0d@Huawei.com>

On Thu, Feb 27, 2020 at 05:43:51PM +0000, Jonathan Cameron wrote:
> On Mon, 24 Feb 2020 19:23:42 +0100
> Jean-Philippe Brucker <jean-philippe@linaro.org> wrote:
> 
> > From: Jean-Philippe Brucker <jean-philippe.brucker@arm.com>
> > 
> > To enable address space sharing with the IOMMU, introduce mm_context_get()
> > and mm_context_put(), that pin down a context and ensure that it will keep
> > its ASID after a rollover. Export the symbols to let the modular SMMUv3
> > driver use them.
> > 
> > Pinning is necessary because a device constantly needs a valid ASID,
> > unlike tasks that only require one when running. Without pinning, we would
> > need to notify the IOMMU when we're about to use a new ASID for a task,
> > and it would get complicated when a new task is assigned a shared ASID.
> > Consider the following scenario with no ASID pinned:
> > 
> > 1. Task t1 is running on CPUx with shared ASID (gen=1, asid=1)
> > 2. Task t2 is scheduled on CPUx, gets ASID (1, 2)
> > 3. Task tn is scheduled on CPUy, a rollover occurs, tn gets ASID (2, 1)
> >    We would now have to immediately generate a new ASID for t1, notify
> >    the IOMMU, and finally enable task tn. We are holding the lock during
> >    all that time, since we can't afford having another CPU trigger a
> >    rollover. The IOMMU issues invalidation commands that can take tens of
> >    milliseconds.
> > 
> > It gets needlessly complicated. All we wanted to do was schedule task tn,
> > that has no business with the IOMMU. By letting the IOMMU pin tasks when
> > needed, we avoid stalling the slow path, and let the pinning fail when
> > we're out of shareable ASIDs.
> > 
> > After a rollover, the allocator expects at least one ASID to be available
> > in addition to the reserved ones (one per CPU). So (NR_ASIDS - NR_CPUS -
> > 1) is the maximum number of ASIDs that can be shared with the IOMMU.
> > 
> > Signed-off-by: Jean-Philippe Brucker <jean-philippe@linaro.org>
> A few more trivial points.

I'll fix those, thanks

Jean

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-03-04 14:10 UTC|newest]

Thread overview: 210+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-24 18:23 [PATCH v4 00/26] iommu: Shared Virtual Addressing and SMMUv3 support Jean-Philippe Brucker
2020-02-24 18:23 ` Jean-Philippe Brucker
2020-02-24 18:23 ` Jean-Philippe Brucker
2020-02-24 18:23 ` [PATCH v4 01/26] mm/mmu_notifiers: pass private data down to alloc_notifier() Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 19:00   ` Jason Gunthorpe
2020-02-24 19:00     ` Jason Gunthorpe
2020-02-24 19:00     ` Jason Gunthorpe
2020-02-25  9:24     ` Jean-Philippe Brucker
2020-02-25  9:24       ` Jean-Philippe Brucker
2020-02-25  9:24       ` Jean-Philippe Brucker
2020-02-25 14:08       ` Jason Gunthorpe
2020-02-25 14:08         ` Jason Gunthorpe
2020-02-25 14:08         ` Jason Gunthorpe
2020-02-28 14:39         ` Jean-Philippe Brucker
2020-02-28 14:39           ` Jean-Philippe Brucker
2020-02-28 14:39           ` Jean-Philippe Brucker
2020-02-28 14:48           ` Jason Gunthorpe
2020-02-28 14:48             ` Jason Gunthorpe
2020-02-28 14:48             ` Jason Gunthorpe
2020-02-28 15:04             ` Jean-Philippe Brucker
2020-02-28 15:04               ` Jean-Philippe Brucker
2020-02-28 15:04               ` Jean-Philippe Brucker
2020-02-28 15:13               ` Jason Gunthorpe
2020-02-28 15:13                 ` Jason Gunthorpe
2020-02-28 15:13                 ` Jason Gunthorpe
2020-03-06  9:56                 ` Jean-Philippe Brucker
2020-03-06  9:56                   ` Jean-Philippe Brucker
2020-03-06  9:56                   ` Jean-Philippe Brucker
2020-03-06 13:09                   ` Jason Gunthorpe
2020-03-06 13:09                     ` Jason Gunthorpe
2020-03-06 13:09                     ` Jason Gunthorpe
2020-03-06 14:35                     ` Jean-Philippe Brucker
2020-03-06 14:35                       ` Jean-Philippe Brucker
2020-03-06 14:35                       ` Jean-Philippe Brucker
2020-03-06 14:52                       ` Jason Gunthorpe
2020-03-06 14:52                         ` Jason Gunthorpe
2020-03-06 14:52                         ` Jason Gunthorpe
2020-03-06 16:15                         ` Jean-Philippe Brucker
2020-03-06 16:15                           ` Jean-Philippe Brucker
2020-03-06 16:15                           ` Jean-Philippe Brucker
2020-03-06 17:42                           ` Jason Gunthorpe
2020-03-06 17:42                             ` Jason Gunthorpe
2020-03-06 17:42                             ` Jason Gunthorpe
2020-03-13 18:49                             ` Jean-Philippe Brucker
2020-03-13 18:49                               ` Jean-Philippe Brucker
2020-03-13 18:49                               ` Jean-Philippe Brucker
2020-03-13 19:13                               ` Jason Gunthorpe
2020-03-13 19:13                                 ` Jason Gunthorpe
2020-03-13 19:13                                 ` Jason Gunthorpe
2020-03-16 15:46                     ` Christoph Hellwig
2020-03-16 15:46                       ` Christoph Hellwig
2020-03-16 15:46                       ` Christoph Hellwig
2020-03-17 18:40                       ` Jason Gunthorpe
2020-03-17 18:40                         ` Jason Gunthorpe
2020-03-17 18:40                         ` Jason Gunthorpe
2020-03-05 16:36   ` Christoph Hellwig
2020-03-05 16:36     ` Christoph Hellwig
2020-03-05 16:36     ` Christoph Hellwig
2020-02-24 18:23 ` [PATCH v4 02/26] iommu/sva: Manage process address spaces Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-26 12:35   ` Jonathan Cameron
2020-02-26 12:35     ` Jonathan Cameron
2020-02-26 12:35     ` Jonathan Cameron
2020-02-28 14:43     ` Jean-Philippe Brucker
2020-02-28 14:43       ` Jean-Philippe Brucker
2020-02-28 14:43       ` Jean-Philippe Brucker
2020-02-28 16:26       ` Jonathan Cameron
2020-02-28 16:26         ` Jonathan Cameron
2020-02-28 16:26         ` Jonathan Cameron
2020-02-26 19:13   ` Jacob Pan
2020-02-26 19:13     ` Jacob Pan
2020-02-26 19:13     ` Jacob Pan
2020-02-28 14:40     ` Jean-Philippe Brucker
2020-02-28 14:40       ` Jean-Philippe Brucker
2020-02-28 14:40       ` Jean-Philippe Brucker
2020-02-28 14:57       ` Jason Gunthorpe
2020-02-28 14:57         ` Jason Gunthorpe
2020-02-28 14:57         ` Jason Gunthorpe
2020-02-24 18:23 ` [PATCH v4 03/26] iommu: Add a page fault handler Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-25  3:30   ` Xu Zaibo
2020-02-25  3:30     ` Xu Zaibo
2020-02-25  3:30     ` Xu Zaibo
2020-02-25  9:25     ` Jean-Philippe Brucker
2020-02-25  9:25       ` Jean-Philippe Brucker
2020-02-25  9:25       ` Jean-Philippe Brucker
2020-02-26  3:05       ` Xu Zaibo
2020-02-26  3:05         ` Xu Zaibo
2020-02-26  3:05         ` Xu Zaibo
2020-02-26 13:59   ` Jonathan Cameron
2020-02-26 13:59     ` Jonathan Cameron
2020-02-26 13:59     ` Jonathan Cameron
2020-02-28 14:44     ` Jean-Philippe Brucker
2020-02-28 14:44       ` Jean-Philippe Brucker
2020-02-28 14:44       ` Jean-Philippe Brucker
2020-02-24 18:23 ` [PATCH v4 04/26] iommu/sva: Search mm by PASID Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23 ` [PATCH v4 05/26] iommu/iopf: Handle mm faults Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23 ` [PATCH v4 06/26] iommu/sva: Register page fault handler Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-26 19:39   ` Jacob Pan
2020-02-26 19:39     ` Jacob Pan
2020-02-26 19:39     ` Jacob Pan
2020-02-28 14:44     ` Jean-Philippe Brucker
2020-02-28 14:44       ` Jean-Philippe Brucker
2020-02-28 14:44       ` Jean-Philippe Brucker
2020-02-24 18:23 ` [PATCH v4 07/26] arm64: mm: Pin down ASIDs for sharing mm with devices Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-27 17:43   ` Jonathan Cameron
2020-02-27 17:43     ` Jonathan Cameron
2020-02-27 17:43     ` Jonathan Cameron
2020-03-04 14:10     ` Jean-Philippe Brucker [this message]
2020-03-04 14:10       ` Jean-Philippe Brucker
2020-03-04 14:10       ` Jean-Philippe Brucker
2020-02-24 18:23 ` [PATCH v4 08/26] iommu/io-pgtable-arm: Move some definitions to a header Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23 ` [PATCH v4 09/26] iommu/arm-smmu-v3: Manage ASIDs with xarray Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23 ` [PATCH v4 10/26] arm64: cpufeature: Export symbol read_sanitised_ftr_reg() Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23 ` [PATCH v4 11/26] iommu/arm-smmu-v3: Share process page tables Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23 ` [PATCH v4 12/26] iommu/arm-smmu-v3: Seize private ASID Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23 ` [PATCH v4 13/26] iommu/arm-smmu-v3: Add support for VHE Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23 ` [PATCH v4 14/26] iommu/arm-smmu-v3: Enable broadcast TLB maintenance Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23 ` [PATCH v4 15/26] iommu/arm-smmu-v3: Add SVA feature checking Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23 ` [PATCH v4 16/26] iommu/arm-smmu-v3: Add dev_to_master() helper Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23 ` [PATCH v4 17/26] iommu/arm-smmu-v3: Implement mm operations Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23 ` [PATCH v4 18/26] iommu/arm-smmu-v3: Hook up ATC invalidation to mm ops Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23 ` [PATCH v4 19/26] iommu/arm-smmu-v3: Add support for Hardware Translation Table Update Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23 ` [PATCH v4 20/26] iommu/arm-smmu-v3: Maintain a SID->device structure Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23 ` [PATCH v4 21/26] iommu/arm-smmu-v3: Ratelimit event dump Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2021-05-28  8:09   ` Aaro Koskinen
2021-05-28  8:09     ` Aaro Koskinen
2021-05-28  8:09     ` Aaro Koskinen
2021-05-28 16:25     ` Jean-Philippe Brucker
2021-05-28 16:25       ` Jean-Philippe Brucker
2021-05-28 16:25       ` Jean-Philippe Brucker
2020-02-24 18:23 ` [PATCH v4 22/26] dt-bindings: document stall property for IOMMU masters Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23 ` [PATCH v4 23/26] iommu/arm-smmu-v3: Add stall support for platform devices Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-26  8:44   ` Xu Zaibo
2020-02-26  8:44     ` Xu Zaibo
2020-02-26  8:44     ` Xu Zaibo
2020-03-04 14:09     ` Jean-Philippe Brucker
2020-03-04 14:09       ` Jean-Philippe Brucker
2020-03-04 14:09       ` Jean-Philippe Brucker
2020-02-27 18:17   ` Jonathan Cameron
2020-02-27 18:17     ` Jonathan Cameron
2020-02-27 18:17     ` Jonathan Cameron
2020-03-04 14:08     ` Jean-Philippe Brucker
2020-03-04 14:08       ` Jean-Philippe Brucker
2020-03-04 14:08       ` Jean-Philippe Brucker
2020-03-09 10:48       ` Jonathan Cameron
2020-03-09 10:48         ` Jonathan Cameron
2020-03-09 10:48         ` Jonathan Cameron
2020-02-24 18:23 ` [PATCH v4 24/26] PCI/ATS: Add PRI stubs Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-24 18:23   ` Jean-Philippe Brucker
2020-02-27 20:55   ` Bjorn Helgaas
2020-02-27 20:55     ` Bjorn Helgaas
2020-02-27 20:55     ` Bjorn Helgaas
2020-02-24 18:24 ` [PATCH v4 25/26] PCI/ATS: Export symbols of PRI functions Jean-Philippe Brucker
2020-02-24 18:24   ` Jean-Philippe Brucker
2020-02-24 18:24   ` Jean-Philippe Brucker
2020-02-27 20:55   ` Bjorn Helgaas
2020-02-27 20:55     ` Bjorn Helgaas
2020-02-27 20:55     ` Bjorn Helgaas
2020-02-24 18:24 ` [PATCH v4 26/26] iommu/arm-smmu-v3: Add support for PRI Jean-Philippe Brucker
2020-02-24 18:24   ` Jean-Philippe Brucker
2020-02-24 18:24   ` Jean-Philippe Brucker
2020-02-27 18:22 ` [PATCH v4 00/26] iommu: Shared Virtual Addressing and SMMUv3 support Jonathan Cameron
2020-02-27 18:22   ` Jonathan Cameron
2020-02-27 18:22   ` Jonathan Cameron

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200304141045.GD646000@myrica \
    --to=jean-philippe@linaro.org \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=catalin.marinas@arm.com \
    --cc=christian.koenig@amd.com \
    --cc=devicetree@vger.kernel.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jacob.jun.pan@linux.intel.com \
    --cc=jean-philippe.brucker@arm.com \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=will@kernel.org \
    --cc=yi.l.liu@intel.com \
    --cc=zhangfei.gao@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.