Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp532351pxj; Fri, 11 Jun 2021 05:28:20 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxJvxXzH2UrdUDzpzpwcKyO4pQVO/wahDz37a4+MXZL9EvB06t3Bte8RsxeHNr/WLTOrAMq X-Received: by 2002:a05:6402:10cc:: with SMTP id p12mr3485211edu.328.1623414500576; Fri, 11 Jun 2021 05:28:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1623414500; cv=none; d=google.com; s=arc-20160816; b=RiZCmUbpIOVyJjV9mH/F2qWVBr/2+f2/+jHUTyPfjcUoPLhqM4bBxQT3mNglDlRWQA qGJIfdmEt8cnRxAWGCVhP+DodwECAHogw+sE5SGb/JNSYih5mKJHGVDerpHIZ6EWDddT VbqWaP9lzT7vmM8et3XeJj5vCVkLpxh7z8uCTW+6k0akZMQHy8mi2L0t98//0c9EN+jf 5YlNaWrgcWayt/Y2XRevXpfkU/aty2zg5zGy96yYM8uIbMh8akMiE7/CH3HdHZkn2A7z SkAHKZT2/pJd9VceJmoOaHAsrYrYj3VrynCOirCNktiRlQkLeDyEjnBl4Eacj6NJO0ga Hi1g== 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=bp2sLQU4cZBQL6+5kyWy+pFg9x6zywpZ6ruSgxy0W3Q=; b=p7N1LrjkgbHPxaIn1wnMvnudH7iKvVbqqmAfNQt6iN38+q3lHJRc2DtpVOfdABqx2t OtP32EktSotN/nisohmR4GqSF8XguzGMw9T2Bd0EhUR6KjZy9waKsd0++C9A7SU32ZRD KDC18dNry64etBi1GnWgXxv1Eps+JsXMkro6OhUF32XrZwkY2ZwbtKnHcHBMhF1Im8FK l20X+YiPLvbcbu07UybqK3WxXbqNI7CXKxaUg2u09v4ORY/xxAYtMhT2sXBRRzQyZSyF 41xX0WlmrddLkhlRaf+5JqsOhHnEbDQQnTwKaTt1gbFXypfQyGV1exTYN3gQ7t6bnXlC XGwg== 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 a16si4674278edy.330.2021.06.11.05.27.57; Fri, 11 Jun 2021 05:28:20 -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 S231626AbhFKM20 (ORCPT + 99 others); Fri, 11 Jun 2021 08:28:26 -0400 Received: from frasgout.his.huawei.com ([185.176.79.56]:3213 "EHLO frasgout.his.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231613AbhFKM2X (ORCPT ); Fri, 11 Jun 2021 08:28:23 -0400 Received: from fraeml703-chm.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4G1frV2X34z6J9Z4; Fri, 11 Jun 2021 20:13:30 +0800 (CST) Received: from lhreml724-chm.china.huawei.com (10.201.108.75) by fraeml703-chm.china.huawei.com (10.206.15.52) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2176.2; Fri, 11 Jun 2021 14:26:21 +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, 11 Jun 2021 13:26:18 +0100 From: John Garry To: , , , , CC: , , , , , John Garry Subject: [PATCH v12 1/5] iommu: Print strict or lazy mode at init time Date: Fri, 11 Jun 2021 20:20:39 +0800 Message-ID: <1623414043-40745-2-git-send-email-john.garry@huawei.com> X-Mailer: git-send-email 2.8.1 In-Reply-To: <1623414043-40745-1-git-send-email-john.garry@huawei.com> References: <1623414043-40745-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: dggems704-chm.china.huawei.com (10.3.19.181) 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 do set the mode via custom means - the AMD and Intel drivers - they still maintain prints to notify the change in policy. Signed-off-by: John Garry --- 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