From: Yi Liu <yi.l.liu@intel.com>
To: Lu Baolu <baolu.lu@linux.intel.com>, <iommu@lists.linux.dev>
Cc: Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
"Robin Murphy" <robin.murphy@arm.com>,
Joel Granados <joel.granados@kernel.org>,
Jason Gunthorpe <jgg@ziepe.ca>, Kevin Tian <kevin.tian@intel.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/1] iommu/vt-d: Drain PRQs when domain removed from RID
Date: Fri, 1 Nov 2024 14:23:28 +0800 [thread overview]
Message-ID: <7e562d1b-9b90-464d-a43b-ee7d13d39824@intel.com> (raw)
In-Reply-To: <20241101045543.70086-1-baolu.lu@linux.intel.com>
On 2024/11/1 12:55, Lu Baolu wrote:
> As this iommu driver now supports page faults for requests without
> PASID, page requests should be drained when a domain is removed from
> the RID2PASID entry.
>
> This results in the intel_iommu_drain_pasid_prq() call being moved to
> intel_pasid_tear_down_entry(). This indicates that when a translation
> is removed from any PASID entry and the PRI has been enabled on the
> device, page requests are drained in the domain detachment path.
>
> The intel_iommu_drain_pasid_prq() helper has been modified to support
> sending device TLB invalidation requests for both PASID and non-PASID
> cases.
>
> Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com>
> ---
> drivers/iommu/intel/iommu.c | 1 -
> drivers/iommu/intel/pasid.c | 1 +
> drivers/iommu/intel/prq.c | 26 +++++++++-----------------
> 3 files changed, 10 insertions(+), 18 deletions(-)
Reviewed-by: Yi Liu <yi.l.liu@intel.com>
--
Regards,
Yi Liu
next prev parent reply other threads:[~2024-11-01 6:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 4:55 [PATCH v2 1/1] iommu/vt-d: Drain PRQs when domain removed from RID Lu Baolu
2024-11-01 6:23 ` Yi Liu [this message]
2024-11-02 3:16 ` Baolu Lu
2024-11-04 8:30 ` Joel Granados
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=7e562d1b-9b90-464d-a43b-ee7d13d39824@intel.com \
--to=yi.l.liu@intel.com \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joel.granados@kernel.org \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--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