From: Dave Jiang <dave.jiang@intel.com>
To: Baolu Lu <baolu.lu@linux.intel.com>,
iommu@lists.linux.dev, dmaengine@vger.kernel.org
Cc: Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Kevin Tian <kevin.tian@intel.com>,
Fenghua Yu <fenghua.yu@intel.com>, Vinod Koul <vkoul@kernel.org>,
Jacob Pan <jacob.jun.pan@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/6] dmaengine: idxd: Add enable/disable device IOPF feature
Date: Mon, 3 Apr 2023 09:57:33 -0700 [thread overview]
Message-ID: <cea7d7ff-bf03-eb7d-a836-b51b9addef5b@intel.com> (raw)
In-Reply-To: <f6445aed-bf35-7245-3d52-336ebe11a866@linux.intel.com>
On 4/2/23 10:49 PM, Baolu Lu wrote:
> 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@intel.com>
>> Reviewed-by: Fenghua Yu<fenghua.yu@intel.com>
>> Reviewed-by: Kevin Tian<kevin.tian@intel.com>
>> Signed-off-by: Lu Baolu<baolu.lu@linux.intel.com>
>
> Hi Dave and Fenghua,
>
> The following iommu patches depends on this one. Can I route it to
> Linus through the iommu tree?
Hi Baolu, you'll need an ack from Vinod, who is the dmaengine subsystem
maintainer. I have no objections.
>
> Best regards,
> baolu
next prev parent reply other threads:[~2023-04-03 16:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 12:02 [PATCH v3 0/6] iommu/vt-d: Refactor code for non-PRI IOPF Lu Baolu
2023-03-24 12:02 ` [PATCH v3 1/6] dmaengine: idxd: Add enable/disable device IOPF feature Lu Baolu
2023-04-03 5:49 ` Baolu Lu
2023-04-03 16:57 ` Dave Jiang [this message]
2023-04-04 5:19 ` Baolu Lu
2023-03-24 12:02 ` [PATCH v3 2/6] iommu/vt-d: Allow SVA with device-specific IOPF Lu Baolu
2023-03-28 2:10 ` Tian, Kevin
2023-03-24 12:02 ` [PATCH v3 3/6] iommu/vt-d: Move iopf code from SVA to IOPF enabling path Lu Baolu
2023-03-24 12:02 ` [PATCH v3 4/6] iommu/vt-d: Move pfsid and ats_qdep calculation to device probe path Lu Baolu
2023-03-24 12:02 ` [PATCH v3 5/6] iommu/vt-d: Move PRI handling to IOPF feature path Lu Baolu
2023-03-28 2:11 ` Tian, Kevin
2023-03-24 12:02 ` [PATCH v3 6/6] iommu/vt-d: Remove unnecessary checks in iopf disabling path Lu Baolu
2023-03-28 2:11 ` Tian, Kevin
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=cea7d7ff-bf03-eb7d-a836-b51b9addef5b@intel.com \
--to=dave.jiang@intel.com \
--cc=baolu.lu@linux.intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=fenghua.yu@intel.com \
--cc=iommu@lists.linux.dev \
--cc=jacob.jun.pan@linux.intel.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=vkoul@kernel.org \
--cc=will@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).