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 4/5] vt-d/iommu: Refactor quirk_extra_dev_tlb_flush()
Date: Fri, 9 Aug 2024 16:25:30 +0800 [thread overview]
Message-ID: <4d1f761b-993d-4c13-a296-111bc3b39141@linux.intel.com> (raw)
In-Reply-To: <20240809025431.14605-5-tina.zhang@intel.com>
On 2024/8/9 10:54, Tina Zhang wrote:
> Extract the core logic from quirk_extra_dev_tlb_flush() into a new
> helper __quirk_extra_dev_tlb_flush(). This helper is for accommodating
> for both individual and batched TLB invalidation commands, thereby
> streamlining the process for handling device-specific TLB flush quirks.
>
> Signed-off-by: Tina Zhang<tina.zhang@intel.com>
> ---
> drivers/iommu/intel/iommu.c | 55 +++++++++++++++++++++++++++++--------
> drivers/iommu/intel/iommu.h | 4 +++
> 2 files changed, 47 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/iommu/intel/iommu.c b/drivers/iommu/intel/iommu.c
> index 9ff8b83c19a3..160d569015b4 100644
> --- a/drivers/iommu/intel/iommu.c
> +++ b/drivers/iommu/intel/iommu.c
> @@ -4875,6 +4875,41 @@ static void __init check_tylersburg_isoch(void)
> vtisochctrl);
> }
>
> +static inline void __quirk_extra_dev_tlb_flush(struct device_domain_info *info,
> + unsigned long address, unsigned long mask,
> + u32 pasid, u16 qdep,
> + struct qi_batch *batch)
> +{
> + u16 sid;
> +
> + if (likely(!info->dtlb_extra_inval))
> + return;
> +
> + sid = PCI_DEVID(info->bus, info->devfn);
> + if (batch == NULL) {
> + if (pasid == IOMMU_NO_PASID)
> + qi_flush_dev_iotlb(info->iommu, sid, info->pfsid,
> + qdep, address, mask);
> + else
> + qi_flush_dev_iotlb_pasid(info->iommu, sid,
> + info->pfsid, pasid,
> + qdep, address, mask);
> + } else {
> + if (pasid == IOMMU_NO_PASID)
> + qi_batch_add_dev_iotlb_desc(info->iommu, sid,
> + info->pfsid, qdep,
> + address, mask, batch);
> + else
> + qi_batch_add_dev_iotlb_pasid_desc(info->iommu,
> + sid,
> + info->pfsid,
> + pasid, qdep,
> + address,
> + mask,
> + batch);
> + }
> +}
How about moving this helper into cache.c? That's its only or major
consumer, right?
By the way, in which case could 'batch' be a NULL?
Thanks,
baolu
next prev parent reply other threads:[~2024-08-09 8:25 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
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 [this message]
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=4d1f761b-993d-4c13-a296-111bc3b39141@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®