public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Baolu Lu <baolu.lu@linux.intel.com>
To: Yi Liu <yi.l.liu@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>
Cc: Dave Jiang <dave.jiang@intel.com>, Vinod Koul <vkoul@kernel.org>,
	Fenghua Yu <fenghuay@nvidia.com>,
	Zhangfei Gao <zhangfei.gao@linaro.org>,
	Zhou Wang <wangzhou1@hisilicon.com>,
	iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 06/12] iommu/vt-d: Cleanup intel_context_flush_present()
Date: Wed, 5 Mar 2025 10:21:24 +0800	[thread overview]
Message-ID: <51cb2ef8-3cce-4af7-b6ce-c3e3d490e6a3@linux.intel.com> (raw)
In-Reply-To: <f7d84e3d-a648-4292-a652-408f704411c7@intel.com>

On 3/4/25 16:43, Yi Liu wrote:
> On 2025/2/24 13:16, Lu Baolu wrote:
>> The intel_context_flush_present() is called in places where either the
>> scalable mode is disabled, or scalable mode is enabled but all PASID
>> entries are known to be non-present. In these cases, the flush_domains
>> path within intel_context_flush_present() will never execute. This dead
>> code is therefore removed.
> 
> The reason for this path is the remaining caller of
> intel_context_flush_present() is only the domain_context_clear_one() which
> is called in legacy mode path. Is it?
> If so, it seems unnecessary to keep __context_flush_dev_iotlb(info); in the
> end of the new intel_context_flush_present(). Also, since this helper is 
> more for legacy mode, might be good to move it out of pasid.c.:)

This helper is for invalidating various caches when a context entry is
present and certain fields are changed. It is used in both legacy and
scalable modes.

In the past, this helper would work even if some PASIDs were still in
use. After the changes introduced in this series, this PASID-in-use case
is removed. So remove the dead code.

Thanks,
baolu

  reply	other threads:[~2025-03-05  2:24 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-24  5:16 [PATCH v2 00/12] iommu: Remove IOMMU_DEV_FEAT_SVA/_IOPF Lu Baolu
2025-02-24  5:16 ` [PATCH v2 01/12] iommu/arm-smmu-v3: Put iopf enablement in the domain attach path Lu Baolu
2025-02-24  5:16 ` [PATCH v2 02/12] iommu/vt-d: Check if SVA is supported when attaching the SVA domain Lu Baolu
2025-02-25  7:23   ` Tian, Kevin
2025-03-04  7:44   ` Yi Liu
2025-02-24  5:16 ` [PATCH v2 03/12] iommu: Remove IOMMU_DEV_FEAT_SVA Lu Baolu
2025-02-25  7:24   ` Tian, Kevin
2025-03-04  7:50   ` Yi Liu
2025-02-24  5:16 ` [PATCH v2 04/12] iommu/vt-d: Move scalable mode ATS enablement to probe path Lu Baolu
2025-02-25  7:28   ` Tian, Kevin
2025-02-26  2:21     ` Baolu Lu
2025-03-04  7:55   ` Yi Liu
2025-02-24  5:16 ` [PATCH v2 05/12] iommu/vt-d: Move PRI enablement in " Lu Baolu
2025-02-25  7:37   ` Tian, Kevin
2025-02-26  3:53     ` Baolu Lu
2025-02-24  5:16 ` [PATCH v2 06/12] iommu/vt-d: Cleanup intel_context_flush_present() Lu Baolu
2025-02-25  7:43   ` Tian, Kevin
2025-02-26  3:57     ` Baolu Lu
2025-02-26  5:17       ` Tian, Kevin
2025-03-04  8:43   ` Yi Liu
2025-03-05  2:21     ` Baolu Lu [this message]
2025-03-05  3:34       ` Yi Liu
2025-03-05  5:36         ` Baolu Lu
2025-02-24  5:16 ` [PATCH v2 07/12] iommu/vt-d: Put iopf enablement in domain attach path Lu Baolu
2025-02-25  8:02   ` Tian, Kevin
2025-02-24  5:16 ` [PATCH v2 08/12] iommufd/selftest: " Lu Baolu
2025-02-25  8:16   ` Tian, Kevin
2025-02-26  4:06     ` Baolu Lu
2025-02-24  5:16 ` [PATCH v2 09/12] dmaengine: idxd: Remove unnecessary IOMMU_DEV_FEAT_IOPF Lu Baolu
2025-02-25  8:16   ` Tian, Kevin
2025-02-24  5:16 ` [PATCH v2 10/12] uacce: " Lu Baolu
2025-02-24 10:00   ` Zhangfei Gao
2025-02-25  8:17   ` Tian, Kevin
2025-02-24  5:16 ` [PATCH v2 11/12] iommufd: " Lu Baolu
2025-02-25  8:18   ` Tian, Kevin
2025-02-24  5:16 ` [PATCH v2 12/12] iommu: Remove iommu_dev_enable/disable_feature() Lu Baolu
2025-02-25  8:18   ` Tian, Kevin
2025-02-24  9:58 ` [PATCH v2 00/12] iommu: Remove IOMMU_DEV_FEAT_SVA/_IOPF Zhangfei Gao

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=51cb2ef8-3cce-4af7-b6ce-c3e3d490e6a3@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=dave.jiang@intel.com \
    --cc=fenghuay@nvidia.com \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@ziepe.ca \
    --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=wangzhou1@hisilicon.com \
    --cc=will@kernel.org \
    --cc=yi.l.liu@intel.com \
    --cc=zhangfei.gao@linaro.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