public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yi Liu <yi.l.liu@intel.com>
To: Joel Granados <joel.granados@kernel.org>,
	David Woodhouse <dwmw2@infradead.org>,
	Lu Baolu <baolu.lu@linux.intel.com>,
	Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
	Robin Murphy <robin.murphy@arm.com>,
	Jason Gunthorpe <jgg@ziepe.ca>, Kevin Tian <kevin.tian@intel.com>,
	Klaus Jensen <its@irrelevant.dk>
Cc: <linux-kernel@vger.kernel.org>, <iommu@lists.linux.dev>,
	Klaus Jensen <k.jensen@samsung.com>
Subject: Re: [PATCH v4 2/5] iommu/vt-d: Remove the pasid present check in prq_event_thread
Date: Mon, 28 Oct 2024 15:50:46 +0800	[thread overview]
Message-ID: <90c772ce-6d2d-4a1d-bfec-5a7813be43e4@intel.com> (raw)
In-Reply-To: <20241015-jag-iopfv8-v4-2-b696ca89ba29@kernel.org>

On 2024/10/16 05:08, Joel Granados wrote:
> From: Klaus Jensen <k.jensen@samsung.com>
> 
> PASID is not strictly needed when handling a PRQ event; remove the check
> for the pasid present bit in the request. This change was not included
> in the creation of prq.c to emphasize the change in capability checks
> when handing PRQ events.
> 
> Signed-off-by: Klaus Jensen <k.jensen@samsung.com>
> Reviewed-by: Kevin Tian <kevin.tian@intel.com>
> Signed-off-by: Joel Granados <joel.granados@kernel.org>

looks like the PRQ draining is missed for the PRI usage. When a pasid
entry is destroyed, it might need to add helper similar to the
intel_drain_pasid_prq() to drain PRQ for the non-pasid usage.

> ---
>   drivers/iommu/intel/prq.c | 12 +++---------
>   1 file changed, 3 insertions(+), 9 deletions(-)
> 
> diff --git a/drivers/iommu/intel/prq.c b/drivers/iommu/intel/prq.c
> index d4f18eb46475..3c50c848893f 100644
> --- a/drivers/iommu/intel/prq.c
> +++ b/drivers/iommu/intel/prq.c
> @@ -223,18 +223,12 @@ static irqreturn_t prq_event_thread(int irq, void *d)
>   		req = &iommu->prq[head / sizeof(*req)];
>   		address = (u64)req->addr << VTD_PAGE_SHIFT;
>   
> -		if (unlikely(!req->pasid_present)) {
> -			pr_err("IOMMU: %s: Page request without PASID\n",
> -			       iommu->name);
> -bad_req:
> -			handle_bad_prq_event(iommu, req, QI_RESP_INVALID);
> -			goto prq_advance;
> -		}
> -
>   		if (unlikely(!is_canonical_address(address))) {
>   			pr_err("IOMMU: %s: Address is not canonical\n",
>   			       iommu->name);
> -			goto bad_req;
> +bad_req:
> +			handle_bad_prq_event(iommu, req, QI_RESP_INVALID);
> +			goto prq_advance;
>   		}
>   
>   		if (unlikely(req->pm_req && (req->rd_req | req->wr_req))) {
> 

-- 
Regards,
Yi Liu

  reply	other threads:[~2024-10-28  7:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-15 21:08 [PATCH v4 0/5] iommu: Enable user space IOPFs in non-PASID and non-svm cases Joel Granados
2024-10-15 21:08 ` [PATCH v4 1/5] iommu/vt-d: Separate page request queue from SVM Joel Granados
2024-10-15 21:08 ` [PATCH v4 2/5] iommu/vt-d: Remove the pasid present check in prq_event_thread Joel Granados
2024-10-28  7:50   ` Yi Liu [this message]
2024-10-28  8:23     ` Baolu Lu
2024-10-29  5:11       ` Yi Liu
2024-10-28 10:24     ` Joel Granados
2024-10-29  3:12       ` Baolu Lu
2024-10-29  5:13         ` Yi Liu
2024-10-29  5:39           ` Baolu Lu
2024-10-30  5:51             ` Yi Liu
2024-10-30  8:32               ` Baolu Lu
2024-10-30 14:28         ` Joel Granados
2024-10-31  3:42           ` Baolu Lu
2024-10-31  9:57           ` Baolu Lu
2024-10-31 11:18             ` Joel Granados
2024-10-31 11:46               ` Baolu Lu
2024-10-15 21:08 ` [PATCH v4 3/5] iommu: kconfig: Move IOMMU_IOPF into INTEL_IOMMU Joel Granados
2024-10-15 21:08 ` [PATCH v4 4/5] iommufd: Enable PRI when doing the iommufd_hwpt_alloc Joel Granados
2024-10-15 21:08 ` [PATCH v4 5/5] iommu/vt-d: drop pasid requirement for prq initialization Joel Granados
2024-11-02  3:27 ` [PATCH v4 0/5] iommu: Enable user space IOPFs in non-PASID and non-svm cases Baolu Lu

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=90c772ce-6d2d-4a1d-bfec-5a7813be43e4@intel.com \
    --to=yi.l.liu@intel.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=dwmw2@infradead.org \
    --cc=iommu@lists.linux.dev \
    --cc=its@irrelevant.dk \
    --cc=jgg@ziepe.ca \
    --cc=joel.granados@kernel.org \
    --cc=joro@8bytes.org \
    --cc=k.jensen@samsung.com \
    --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