[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f6445aed-bf35-7245-3d52-336ebe11a866@linux.intel.com>
Date: Mon, 3 Apr 2023 13:49:22 +0800
From: Baolu Lu <baolu.lu@...ux.intel.com>
To: iommu@...ts.linux.dev, dmaengine@...r.kernel.org
Cc: baolu.lu@...ux.intel.com, Joerg Roedel <joro@...tes.org>,
Will Deacon <will@...nel.org>,
Robin Murphy <robin.murphy@....com>,
Kevin Tian <kevin.tian@...el.com>,
Fenghua Yu <fenghua.yu@...el.com>,
Dave Jiang <dave.jiang@...el.com>,
Vinod Koul <vkoul@...nel.org>,
Jacob Pan <jacob.jun.pan@...ux.intel.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 1/6] dmaengine: idxd: Add enable/disable device IOPF
feature
On 3/24/23 8:02 PM, Lu Baolu wrote:
> The iommu subsystem requires IOMMU_DEV_FEAT_IOPF must be enabled before
> and disabled after IOMMU_DEV_FEAT_SVA, if device's I/O page faults rely
> on the IOMMU. Add explicit IOMMU_DEV_FEAT_IOPF enabling/disabling in this
> driver.
>
> At present, missing IOPF enabling/disabling doesn't cause any real issue,
> because the IOMMU driver places the IOPF enabling/disabling in the path
> of SVA feature handling. But this may change.
>
> Reviewed-by: Dave Jiang<dave.jiang@...el.com>
> Reviewed-by: Fenghua Yu<fenghua.yu@...el.com>
> Reviewed-by: Kevin Tian<kevin.tian@...el.com>
> Signed-off-by: Lu Baolu<baolu.lu@...ux.intel.com>
Hi Dave and Fenghua,
The following iommu patches depends on this one. Can I route it to
Linus through the iommu tree?
Best regards,
baolu
Powered by blists - more mailing lists