Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   korantwork@gmail.com
To:     dave.hansen@linux.intel.com, tglx@linutronix.de
Cc:     linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
        trivial@kernel.org, Xinghui Li <korantli@tencent.com>
Subject: [PATCH] x86,iommu:cleanup misleading comment about SWIOTLB turned off by IOMMU
Date:   Wed, 15 Jun 2022 17:06:39 +0800
Message-Id: <20220615090639.34402-1-korantwork@gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

From: Xinghui Li <korantli@tencent.com>

According to commit 327d5b2fee91 ("iommu/vt-d: Allow 32bit devices to
uses DMA domain"), SWIOTLB could be enable even IOMMU exist.This comment
could mislead developer that there is an error enabling SWIOTLB when
they enable IOMMU.

Signed-off-by: Xinghui Li <korantli@tencent.com>
---
 arch/x86/kernel/pci-dma.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/arch/x86/kernel/pci-dma.c b/arch/x86/kernel/pci-dma.c
index 30bbe4abb5d6..c0434abf7e09 100644
--- a/arch/x86/kernel/pci-dma.c
+++ b/arch/x86/kernel/pci-dma.c
@@ -193,7 +193,6 @@ static int __init pci_iommu_init(void)
 	x86_init.iommu.iommu_init();
 
 #ifdef CONFIG_SWIOTLB
-	/* An IOMMU turned us off. */
 	if (x86_swiotlb_enable) {
 		pr_info("PCI-DMA: Using software bounce buffering for IO (SWIOTLB)\n");
 		swiotlb_print_info();
-- 
2.25.1