public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Baolu Lu <baolu.lu@linux.intel.com>
To: Yi Liu <yi.l.liu@intel.com>, Joerg Roedel <joro@8bytes.org>,
	Will Deacon <will@kernel.org>,
	Robin Murphy <robin.murphy@arm.com>,
	Kevin Tian <kevin.tian@intel.com>
Cc: baolu.lu@linux.intel.com, iommu@lists.linux.dev,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2 1/1] iommu/vt-d: Make intel_iommu_drain_pasid_prq() cover faults for RID
Date: Wed, 5 Feb 2025 10:28:35 +0800	[thread overview]
Message-ID: <941d401c-c009-4dcf-bb93-00c25490dd38@linux.intel.com> (raw)
In-Reply-To: <3cca401b-e274-471b-8910-bb30873ead1b@intel.com>

On 2025/1/21 15:01, Yi Liu wrote:
> On 2025/1/21 10:31, Lu Baolu wrote:
>> This driver supports page faults on PCI RID since commit <9f831c16c69e>
>> ("iommu/vt-d: Remove the pasid present check in prq_event_thread") by
>> allowing the reporting of page faults with the pasid_present field 
>> cleared
>> to the upper layer for further handling. The fundamental assumption here
>> is that the detach or replace operations act as a fence for page faults.
>> This implies that all pending page faults associated with a specific RID
>> or PASID are flushed when a domain is detached or replaced from a device
>> RID or PASID.
>>
>> However, the intel_iommu_drain_pasid_prq() helper does not correctly
>> handle faults for RID. This leads to faults potentially remaining pending
>> in the iommu hardware queue even after the domain is detached, thereby
>> violating the aforementioned assumption.
>>
>> Fix this issue by extending intel_iommu_drain_pasid_prq() to cover faults
>> for RID.
>>
>> Fixes: 9f831c16c69e ("iommu/vt-d: Remove the pasid present check in 
>> prq_event_thread")
>> Cc: stable@vger.kernel.org
>> Suggested-by: Kevin Tian <kevin.tian@intel.com>
>> Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com>
>> Reviewed-by: Kevin Tian <kevin.tian@intel.com>
>> ---
>>   drivers/iommu/intel/prq.c | 4 +++-
>>   1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> Change log:
>> v2:
>>   - Add check on page faults targeting RID.
>>
>> v1: https://lore.kernel.org/linux-iommu/20250120080144.810455-1- 
>> baolu.lu@linux.intel.com/
>>
>> diff --git a/drivers/iommu/intel/prq.c b/drivers/iommu/intel/prq.c
>> index c2d792db52c3..064194399b38 100644
>> --- a/drivers/iommu/intel/prq.c
>> +++ b/drivers/iommu/intel/prq.c
>> @@ -87,7 +87,9 @@ void intel_iommu_drain_pasid_prq(struct device *dev, 
>> u32 pasid)
>>           struct page_req_dsc *req;
>>           req = &iommu->prq[head / sizeof(*req)];
>> -        if (!req->pasid_present || req->pasid != pasid) {
>> +        if (req->rid != sid ||
> 
> Does intel-iommu driver managed pasid per-bdf? or global? If the prior one,
> the rid check is needed even in the old time that does not PRIs in the RID
> path.

Do you mean that this fix should be back ported farther than the fix tag
commit?

The iommu driver doesn't manage the PASID. IOMMUFD and SVA do actually.
The SVA uses global PASID. IOMMUFD doesn't yet support PASIDs, pending
the merging of your patches. Therefore, per-BDF PASID management is not
currently implemented in the Linux tree. Anything I overlooked?

---
baolu

  reply	other threads:[~2025-02-05  2:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-21  2:31 [PATCH v2 1/1] iommu/vt-d: Make intel_iommu_drain_pasid_prq() cover faults for RID Lu Baolu
2025-01-21  7:01 ` Yi Liu
2025-02-05  2:28   ` Baolu Lu [this message]
2025-02-11  9:02     ` Yi Liu

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=941d401c-c009-4dcf-bb93-00c25490dd38@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=stable@vger.kernel.org \
    --cc=will@kernel.org \
    --cc=yi.l.liu@intel.com \
    /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