From: Jacob Pan <jacob.jun.pan@linux.intel.com>
To: Lu Baolu <baolu.lu@linux.intel.com>
Cc: iommu@lists.linux.dev, dmaengine@vger.kernel.org,
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>,
Dave Jiang <dave.jiang@intel.com>, Vinod Koul <vkoul@kernel.org>,
linux-kernel@vger.kernel.org, jacob.jun.pan@linux.intel.com
Subject: Re: [PATCH v2 4/5] iommu/vt-d: Move pfsid and ats_qdep calculation to device probe path
Date: Mon, 20 Mar 2023 09:11:27 -0700 [thread overview]
Message-ID: <20230320091127.63dec1fa@jacob-builder> (raw)
In-Reply-To: <20230309025639.26109-5-baolu.lu@linux.intel.com>
Hi BaoLu,
On Thu, 9 Mar 2023 10:56:38 +0800, Lu Baolu <baolu.lu@linux.intel.com>
wrote:
> They should be part of the per-device iommu private data initialization.
>
Reviewed-by: Jacob Pan <jacob.jun.pan@linux.intel.com>
> Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com>
> ---
> drivers/iommu/intel/iommu.c | 26 +++++++++++---------------
> 1 file changed, 11 insertions(+), 15 deletions(-)
>
> diff --git a/drivers/iommu/intel/iommu.c b/drivers/iommu/intel/iommu.c
> index 9ada12bf38dd..fb64ab8358a9 100644
> --- a/drivers/iommu/intel/iommu.c
> +++ b/drivers/iommu/intel/iommu.c
> @@ -1406,20 +1406,6 @@ static void iommu_enable_pci_caps(struct
> device_domain_info *info) return;
>
> pdev = to_pci_dev(info->dev);
> - /* For IOMMU that supports device IOTLB throttling (DIT), we
> assign
> - * PFSID to the invalidation desc of a VF such that IOMMU HW can
> gauge
> - * queue depth at PF level. If DIT is not set, PFSID will be
> treated as
> - * reserved, which should be set to 0.
> - */
> - if (!ecap_dit(info->iommu->ecap))
> - info->pfsid = 0;
> - else {
> - struct pci_dev *pf_pdev;
> -
> - /* pdev will be returned if device is not a vf */
> - pf_pdev = pci_physfn(pdev);
> - info->pfsid = pci_dev_id(pf_pdev);
> - }
>
> /* The PCIe spec, in its wisdom, declares that the behaviour of
> the device if you enable PASID support after ATS support is
> @@ -1438,7 +1424,6 @@ static void iommu_enable_pci_caps(struct
> device_domain_info *info) !pci_enable_ats(pdev, VTD_PAGE_SHIFT)) {
> info->ats_enabled = 1;
> domain_update_iotlb(info->domain);
> - info->ats_qdep = pci_ats_queue_depth(pdev);
> }
> }
>
> @@ -4521,6 +4506,17 @@ static struct iommu_device
> *intel_iommu_probe_device(struct device *dev) dmar_ats_supported(pdev,
> iommu)) { info->ats_supported = 1;
> info->dtlb_extra_inval =
> dev_needs_extra_dtlb_flush(pdev); +
> + /*
> + * For IOMMU that supports device IOTLB
> throttling
> + * (DIT), we assign PFSID to the invalidation
> desc
> + * of a VF such that IOMMU HW can gauge queue
> depth
> + * at PF level. If DIT is not set, PFSID will be
> + * treated as reserved, which should be set to 0.
> + */
> + if (ecap_dit(iommu->ecap))
> + info->pfsid =
> pci_dev_id(pci_physfn(pdev));
> + info->ats_qdep = pci_ats_queue_depth(pdev);
> }
> if (sm_supported(iommu)) {
> if (pasid_supported(iommu)) {
Thanks,
Jacob
next prev parent reply other threads:[~2023-03-20 16:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 2:56 [PATCH v2 0/5] Refactor code for non-PRI IOPF Lu Baolu
2023-03-09 2:56 ` [PATCH v2 1/5] dmaengine: idxd: Add enable/disable device IOPF feature Lu Baolu
2023-03-09 3:51 ` Fenghua Yu
2023-03-16 7:08 ` Tian, Kevin
2023-03-09 2:56 ` [PATCH v2 2/5] iommu/vt-d: Allow SVA with device-specific IOPF Lu Baolu
2023-03-16 7:09 ` Tian, Kevin
2023-03-16 7:31 ` Baolu Lu
2023-03-20 16:00 ` Jacob Pan
2023-03-21 5:43 ` Baolu Lu
2023-03-09 2:56 ` [PATCH v2 3/5] iommu/vt-d: Move iopf code from SVA to IOPF enabling path Lu Baolu
2023-03-16 7:10 ` Tian, Kevin
2023-03-09 2:56 ` [PATCH v2 4/5] iommu/vt-d: Move pfsid and ats_qdep calculation to device probe path Lu Baolu
2023-03-16 7:10 ` Tian, Kevin
2023-03-20 16:11 ` Jacob Pan [this message]
2023-03-09 2:56 ` [PATCH v2 5/5] iommu/vt-d: Move PRI handling to IOPF feature path Lu Baolu
2023-03-16 7:17 ` Tian, Kevin
2023-03-16 8:17 ` Baolu Lu
2023-03-17 0:06 ` Tian, Kevin
2023-03-17 0:47 ` Baolu Lu
2023-03-20 16:28 ` Jacob Pan
2023-03-09 3:01 ` [PATCH v2 0/5] Refactor code for non-PRI IOPF 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=20230320091127.63dec1fa@jacob-builder \
--to=jacob.jun.pan@linux.intel.com \
--cc=baolu.lu@linux.intel.com \
--cc=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=fenghua.yu@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.