From: Baolu Lu <baolu.lu@linux.intel.com>
To: Tina Zhang <tina.zhang@intel.com>, Kevin Tian <kevin.tian@intel.com>
Cc: baolu.lu@linux.intel.com, iommu@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/5] iommu/vt-d: Introduce interfaces for QI batching operations
Date: Fri, 9 Aug 2024 16:15:58 +0800 [thread overview]
Message-ID: <41eda769-f1cf-4e96-9cf7-d74d4802eaf5@linux.intel.com> (raw)
In-Reply-To: <20240809025431.14605-4-tina.zhang@intel.com>
On 2024/8/9 10:54, Tina Zhang wrote:
> Introduces qi_batch_xxx() interfaces to the VT-d driver to enhance the
> efficiency of IOTLB and Dev-IOTLB invalidation command processing.
> By allowing these commands to be batched together before submission,
> the patch aims to minimize the overhead previously incurred when
> handling these operations individually.
>
> The addition of qi_batch_add_xxx() functions enable the accumulation of
> invalidation commands into a batch, while the qi_batch_flush_descs()
> function allows for the collective submission of these commands.
>
> Signed-off-by: Tina Zhang<tina.zhang@intel.com>
> ---
> drivers/iommu/intel/dmar.c | 78 +++++++++++++++++++++++++++++++++++++
> drivers/iommu/intel/iommu.h | 39 +++++++++++++++++++
> 2 files changed, 117 insertions(+)
>
> diff --git a/drivers/iommu/intel/dmar.c b/drivers/iommu/intel/dmar.c
> index 64724af1a618..8d55c49382fc 100644
> --- a/drivers/iommu/intel/dmar.c
> +++ b/drivers/iommu/intel/dmar.c
> @@ -1636,6 +1636,84 @@ void qi_flush_iotlb(struct intel_iommu *iommu, u16 did, u64 addr,
> qi_submit_sync(iommu, &desc, 1, 0);
> }
>
> +static void qi_batch_increment_index(struct intel_iommu *iommu,
> + struct qi_batch *batch)
> +{
> + if (++batch->index == QI_MAX_BATCHED_DESC_COUNT)
> + qi_batch_flush_descs(iommu, batch);
> +}
> +
> +void qi_batch_flush_descs(struct intel_iommu *iommu, struct qi_batch *batch)
> +{
> + if (!batch->index)
> + return;
> +
> + qi_submit_sync(iommu, batch->descs, batch->index, 0);
> +
> + /* Reset the index value and clean the whole batch buffer */
> + memset(batch, 0, sizeof(struct qi_batch));
> +}
> +
> +void qi_batch_add_iotlb_desc(struct intel_iommu *iommu, u16 did, u64 addr,
> + unsigned int size_order, u64 type,
> + struct qi_batch *batch)
> +{
> + qi_desc_iotlb(iommu, did, addr, size_order, type, &(batch->descs[batch->index]));
> + qi_batch_increment_index(iommu, batch);
> +}
> +
> +void qi_batch_add_dev_iotlb_desc(struct intel_iommu *iommu, u16 sid,
> + u16 pfsid, u16 qdep, u64 addr,
> + unsigned int mask,
> + struct qi_batch *batch)
> +{
> + /*
> + * According to VT-d spec, software is recommended to not submit any Device-TLB
> + * invalidation requests while address remapping hardware is disabled.
> + */
> + if (!(iommu->gcmd & DMA_GCMD_TE))
> + return;
> +
> + qi_desc_dev_iotlb(sid, pfsid, qdep, addr, mask, &(batch->descs[batch->index]));
> + qi_batch_increment_index(iommu, batch);
> +}
> +
> +void qi_batch_add_piotlb_desc(struct intel_iommu *iommu, u16 did,
> + u32 pasid, u64 addr,
> + unsigned long npages, bool ih,
> + struct qi_batch *batch)
> +{
> + /*
> + * npages == -1 means a PASID-selective invalidation, otherwise,
> + * a positive value for Page-selective-within-PASID invalidation.
> + * 0 is not a valid input.
> + */
> + if (!npages)
> + return;
> +
> + qi_desc_piotlb(did, pasid, addr, npages, ih, &(batch->descs[batch->index]));
> + qi_batch_increment_index(iommu, batch);
> +}
> +
> +void qi_batch_add_dev_iotlb_pasid_desc(struct intel_iommu *iommu,
> + u16 sid, u16 pfsid,
> + u32 pasid, u16 qdep,
> + u64 addr, unsigned int size_order,
> + struct qi_batch *batch)
> +{
> + /*
> + * According to VT-d spec, software is recommended to not submit any Device-TLB
> + * invalidation requests while address remapping hardware is disabled.
> + */
> + if (!(iommu->gcmd & DMA_GCMD_TE))
> + return;
> +
> + qi_desc_dev_iotlb_pasid(sid, pfsid, pasid,
> + qdep, addr, size_order,
> + &(batch->descs[batch->index]));
> + qi_batch_increment_index(iommu, batch);
> +}
How about moving all these helpers into drivers/iommu/intel/cache.c?
It's the only consumer for these helpers, right?
Thanks,
baolu
next prev parent reply other threads:[~2024-08-09 8:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 2:54 [PATCH v2 0/5] Batch IOTLB/dev-IOTLB invalidation Tina Zhang
2024-08-09 2:54 ` [PATCH v2 1/5] iommu/vt-d: Refactor IOTLB/Dev-IOTLB invalidation command logic Tina Zhang
2024-08-09 2:54 ` [PATCH v2 2/5] iommu/vt-d: Refactor IOTLB and Dev-IOTLB flush logic Tina Zhang
2024-08-09 8:09 ` Baolu Lu
2024-08-09 2:54 ` [PATCH v2 3/5] iommu/vt-d: Introduce interfaces for QI batching operations Tina Zhang
2024-08-09 8:15 ` Baolu Lu [this message]
2024-08-09 8:59 ` Zhang, Tina
2024-08-09 2:54 ` [PATCH v2 4/5] vt-d/iommu: Refactor quirk_extra_dev_tlb_flush() Tina Zhang
2024-08-09 8:25 ` Baolu Lu
2024-08-09 9:10 ` Zhang, Tina
2024-08-09 2:54 ` [PATCH v2 5/5] vt-d/iommu: Enable batching of IOTLB/Dev-IOTLB invalidations Tina Zhang
2024-08-09 8:22 ` Baolu Lu
2024-08-09 9:24 ` Zhang, Tina
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=41eda769-f1cf-4e96-9cf7-d74d4802eaf5@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tina.zhang@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
all inboxes | Powered by JetHome®