From: Kevin Tian <kevin.tian@intel.com>
To: Lu Baolu <baolu.lu@linux.intel.com>,
Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>
Cc: Kevin Tian <kevin.tian@intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Ashok Raj <ashok.raj@intel.com>,
Chris Wright <chrisw@sous-sol.org>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Asit Mallick <asit.k.mallick@intel.com>,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH v2 3/9] iommu/vt-d: Remove dead code when CONFIG_INTEL_IOMMU is not set
Date: Thu, 2 Jul 2026 06:12:10 +0000 [thread overview]
Message-ID: <20260702061216.388743-4-kevin.tian@intel.com> (raw)
In-Reply-To: <20260702061216.388743-1-kevin.tian@intel.com>
Those are leftovers and unreachable now: the entire intel directory
is built only when CONFIG_INTEL_IOMMU is set.
Signed-off-by: Kevin Tian <kevin.tian@intel.com>
---
drivers/iommu/intel/iommu.h | 15 ---------------
1 file changed, 15 deletions(-)
diff --git a/drivers/iommu/intel/iommu.h b/drivers/iommu/intel/iommu.h
index 2cee36138d6e..785aa3b62055 100644
--- a/drivers/iommu/intel/iommu.h
+++ b/drivers/iommu/intel/iommu.h
@@ -1340,7 +1340,6 @@ static inline bool intel_domain_is_ss_paging(struct dmar_domain *domain)
return domain->domain.ops == &intel_ss_paging_domain_ops;
}
-#ifdef CONFIG_INTEL_IOMMU
extern int intel_iommu_sm;
int iommu_calculate_agaw(struct intel_iommu *iommu);
int iommu_calculate_max_sagaw(struct intel_iommu *iommu);
@@ -1355,20 +1354,6 @@ static inline bool ecmd_has_pmu_essential(struct intel_iommu *iommu)
extern int dmar_disabled;
extern int intel_iommu_enabled;
extern int intel_iommu_tboot_noforce;
-#else
-static inline int iommu_calculate_agaw(struct intel_iommu *iommu)
-{
- return 0;
-}
-static inline int iommu_calculate_max_sagaw(struct intel_iommu *iommu)
-{
- return 0;
-}
-#define dmar_disabled (1)
-#define intel_iommu_enabled (0)
-#define intel_iommu_sm (0)
-#define intel_iommu_tboot_noforce (0)
-#endif
static inline const char *decode_prq_descriptor(char *str, size_t size,
u64 dw0, u64 dw1, u64 dw2, u64 dw3)
--
2.43.0
next prev parent reply other threads:[~2026-07-02 6:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 6:12 [PATCH v2 0/9] iommu/vt-d: Support a new DMAR flag Kevin Tian
2026-07-02 6:12 ` [PATCH v2 1/9] iommu/vt-d: Fix no_iommu to disable platform optin Kevin Tian
2026-07-02 6:12 ` [PATCH v2 2/9] iommu/vt-d: Force requesting ACS when tboot is enabled Kevin Tian
2026-07-02 6:50 ` Tian, Kevin
2026-07-02 6:12 ` Kevin Tian [this message]
2026-07-02 6:12 ` [PATCH v2 4/9] iommu/vt-d: Consolidate dmar policy management and force_on logic Kevin Tian
2026-07-02 6:12 ` [PATCH v2 5/9] iommu/vt-d: Use dmar_can_force_on() for platform optin Kevin Tian
2026-07-02 6:12 ` [PATCH v2 6/9] iommu/vt-d: Call dmar_can_force_on() for tboot optin Kevin Tian
2026-07-02 6:12 ` [PATCH v2 7/9] iommu/vt-d: Remove the 'force_on' variable Kevin Tian
2026-07-02 6:12 ` [PATCH v2 8/9] iommu/vt-d: Remove dmar_disabled Kevin Tian
2026-07-02 6:12 ` [PATCH v2 9/9] iommu/vt-d: Support the new DMA_REMAP_OPT_OUT flag bit Kevin Tian
2026-07-27 3:04 ` [PATCH v2 0/9] iommu/vt-d: Support a new DMAR flag 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=20260702061216.388743-4-kevin.tian@intel.com \
--to=kevin.tian@intel.com \
--cc=ashok.raj@intel.com \
--cc=asit.k.mallick@intel.com \
--cc=baolu.lu@linux.intel.com \
--cc=chrisw@sous-sol.org \
--cc=iommu@lists.linux.dev \
--cc=jbarnes@virtuousgeek.org \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--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
all inboxes | Powered by JetHome®