Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp1367180pxj; Fri, 18 Jun 2021 05:46:58 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzGXKKKGZcjMpGgAuC+iawebfqNO8RAge2Zhye0TFGAj7OPBTG3r/kfvb6ldtk/286cAQy1 X-Received: by 2002:aa7:d60a:: with SMTP id c10mr4630038edr.369.1624020418265; Fri, 18 Jun 2021 05:46:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1624020418; cv=none; d=google.com; s=arc-20160816; b=rDC0fMIYanCOStEfKwAIM92VBUsOm0VTfw9pB6LyZWrPR3EheamF8d9yKESS+2sOM4 akQdnnJw3Gjb+MP1ou5PWxASnmvuOoX6AT8T9GcMd782K2r6XCuDA0aqPq3MLXFaHV+X PTCRzSXPpaCCzh8LCZ1cocNiTL0A7GiFOfj4wv9TnIWadX44532uHyUUmmfzX8fBUWKf sQfiaBlqXXLGMZrmqvH7/Uv9YmnH8/juRk8GsrVmB0nV5k8FynwnoCzC388IjXLPFSvu Dq8KpQXudrMJvbVIJRe1Gk8cB6PBGt5xmEw97TPBJ/QABSMcrzmtgH1BSsYOLsQbmjn3 DMLw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:references:in-reply-to:message-id :date:subject:cc:to:from; bh=b0ogG0nc+WEEmVjug9Pd4MkFAvY9BVeJfW6JUNFtvEo=; b=GBDVi9biR5eSlkbV5zAd5xkPM8jMUcMo4tGxjJ0hGVRMTfPkxUKgAoO23PUDjOmMzl 98M6Xo+RU8et91pMEYrZHZ3DcntkMk6IvMPGleyUoL2i6k5szvCd/J5Xx6t7H6HgMIm3 UQa0YiqaB24jmBEcI4LFK2NluUI/KHy9tpwPRYcxGjVMjshhMPVGBy04dOutcyj3ODln gx0fUiNjeoNgt/Wii0MXRJRHmQBiqATJ65KFC7SQYvry36WGxlWju7FH5zdSjJtaZqEb TanyxE2slSnTyAwV33j7SR+v6KLHx2DPVHeT4sLRYoqVXBbShJiaryeeGMogLy+frg1r o7bw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=huawei.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id o7si8437317edq.367.2021.06.18.05.46.35; Fri, 18 Jun 2021 05:46:58 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=huawei.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234088AbhFRLlQ (ORCPT + 99 others); Fri, 18 Jun 2021 07:41:16 -0400 Received: from frasgout.his.huawei.com ([185.176.79.56]:3272 "EHLO frasgout.his.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234095AbhFRLlM (ORCPT ); Fri, 18 Jun 2021 07:41:12 -0400 Received: from fraeml710-chm.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4G5xSD5NJXz6G9rq; Fri, 18 Jun 2021 19:25:48 +0800 (CST) Received: from lhreml724-chm.china.huawei.com (10.201.108.75) by fraeml710-chm.china.huawei.com (10.206.15.59) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Fri, 18 Jun 2021 13:39:01 +0200 Received: from localhost.localdomain (10.69.192.58) by lhreml724-chm.china.huawei.com (10.201.108.75) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Fri, 18 Jun 2021 12:38:57 +0100 From: John Garry To: , , , , , CC: , , , , , , John Garry Subject: [PATCH v14 2/6] iommu: Print strict or lazy mode at init time Date: Fri, 18 Jun 2021 19:34:14 +0800 Message-ID: <1624016058-189713-3-git-send-email-john.garry@huawei.com> X-Mailer: git-send-email 2.8.1 In-Reply-To: <1624016058-189713-1-git-send-email-john.garry@huawei.com> References: <1624016058-189713-1-git-send-email-john.garry@huawei.com> MIME-Version: 1.0 Content-Type: text/plain X-Originating-IP: [10.69.192.58] X-ClientProxiedBy: dggems702-chm.china.huawei.com (10.3.19.179) To lhreml724-chm.china.huawei.com (10.201.108.75) X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org As well as the default domain type, it's useful to know whether strict or lazy for DMA domains, so add this info in a separate print. The (stict/lazy) mode may be also set via iommu.strict earlyparm, but this will be processed prior to iommu_subsys_init(), so that print will be accurate for drivers which don't set the mode via custom means. For the drivers which set the mode via custom means - AMD and Intel drivers - they maintain prints to inform a change in policy or that custom cmdline methods to change policy are deprecated. Signed-off-by: John Garry Reviewed-by: Robin Murphy --- drivers/iommu/iommu.c | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c index 5419c4b9f27a..cf58949cc2f3 100644 --- a/drivers/iommu/iommu.c +++ b/drivers/iommu/iommu.c @@ -138,6 +138,11 @@ static int __init iommu_subsys_init(void) (iommu_cmd_line & IOMMU_CMD_LINE_DMA_API) ? "(set via kernel command line)" : ""); + pr_info("DMA domain TLB invalidation policy: %s mode %s\n", + iommu_dma_strict ? "strict" : "lazy", + (iommu_cmd_line & IOMMU_CMD_LINE_STRICT) ? + "(set via kernel command line)" : ""); + return 0; } subsys_initcall(iommu_subsys_init); -- 2.26.2