Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp2788534pxj; Mon, 14 Jun 2021 07:13:27 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy9E+tknps6cS+szE/9RNtDZQDpxapR6LR8wGzlQUG7zkAiMXxPSsIA7CAp77tbFEarnMtB X-Received: by 2002:a17:906:489:: with SMTP id f9mr15071487eja.508.1623680007337; Mon, 14 Jun 2021 07:13:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1623680007; cv=none; d=google.com; s=arc-20160816; b=XPKQu24tXimv9fFIzd7ouf5Px9ZvUb62eqFvW7N5TYcI0TOZtTsZQ/7pzYwm+klFfi IBnc/0kXp6fVubFL+7gt5k6idjFsUstp8bnF7BLTKSXQ12qv/qxY66wYQDs8VW9IkgiS yFSDHs++CAmon/eCSKjoqYJ1qI7ut/TusFwAIkYPIbpLHj0tJECGxckfs4/A3T8Rma1Q 44BRIb0nfbJcNR2L03aaCIRJpkqAHLqiLkJ2vsODtKgSwhnuUIwedMogNUvtA6EK/UHF peQiL2VoK2FUTBVeSMHgxonkyRCVHPvWeHXRji3Vb+fHyqO8xSkCT2Z3iv7wqvvyJfDU AHyQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=9HbEc6WhOAxC1pjGw5ySJmA9Uv9fLkNmv3PGreWnGD0=; b=oi11lyeDIp/PNxMR22M861b4VYZ0RRLT/rIhcL76R+81FD8qr5uInrR9sU05y45XoO 9v9GTD8YlQKa878nkDv1qvhIg2awW7li/AQTdzNhpQhGjKH7IoZABVxvSCFYwyH/2S+j VvjnvxBcl98dalvShrkrvlN5E9HsX4znbaSBOc5rmiCuyQVz+f+gJQeBf2tK9XZONVe7 c6DJKawbIzC5ndELRMBBvwt4drPnQsv3cGOj1jBlsXwd+oaq1L6UlO8IZ9RMMGOGKkZo 9TutPUKTycAcVejI0KjN8lKBczshDEuirhtWfdM3FrOB+aglvInqvTh3biSCAxVJa4Xa A5gQ== 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=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id ar25si8496466ejc.75.2021.06.14.07.13.04; Mon, 14 Jun 2021 07:13:27 -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=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234403AbhFNON6 (ORCPT + 99 others); Mon, 14 Jun 2021 10:13:58 -0400 Received: from foss.arm.com ([217.140.110.172]:37150 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234035AbhFNON4 (ORCPT ); Mon, 14 Jun 2021 10:13:56 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 0969C1FB; Mon, 14 Jun 2021 07:11:53 -0700 (PDT) Received: from [10.57.9.136] (unknown [10.57.9.136]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 7F9373F70D; Mon, 14 Jun 2021 07:11:51 -0700 (PDT) Subject: Re: [PATCH v12 3/5] iommu/vt-d: Add support for IOMMU default DMA mode build options To: John Garry , Lu Baolu , joro@8bytes.org, will@kernel.org, dwmw2@infradead.org Cc: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org, linuxarm@huawei.com, thunder.leizhen@huawei.com, chenxiang66@hisilicon.com References: <1623414043-40745-1-git-send-email-john.garry@huawei.com> <1623414043-40745-4-git-send-email-john.garry@huawei.com> <4f2cec34-bad9-e1bf-85c1-04d1a0c1aecf@linux.intel.com> <6055cd0d-a1d3-a73a-6831-3837021f3c9c@huawei.com> From: Robin Murphy Message-ID: <0a04f964-80f4-7b2a-9740-eae4596e4e09@arm.com> Date: Mon, 14 Jun 2021 15:11:46 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:78.0) Gecko/20100101 Thunderbird/78.10.1 MIME-Version: 1.0 In-Reply-To: <6055cd0d-a1d3-a73a-6831-3837021f3c9c@huawei.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2021-06-14 08:53, John Garry wrote: > On 12/06/2021 03:22, Lu Baolu wrote: >> On 2021/6/11 20:20, John Garry wrote: >>> @@ -453,8 +452,7 @@ static int __init intel_iommu_setup(char *str) >>>               pr_warn("intel_iommu=forcedac deprecated; use >>> iommu.forcedac instead\n"); >>>               iommu_dma_forcedac = true; >>>           } else if (!strncmp(str, "strict", 6)) { >>> -            pr_info("Disable batched IOTLB flush\n"); >>> -            intel_iommu_strict = 1; >>> +            iommu_set_dma_strict(true); >> >> I would like to deprecate this command line and ask users to use >> iommu.strict instead. > > ok, but then I should probably make the AMD driver also officially > support this. Oops, I should have documented that "iommu.strict" already applies to x86 as well. The interaction with the driver-specific parameters is a bit weird and unintuitive, but it was done knowingly. Let me quickly spin a kernel-parameters.txt fix for that... Cheers, Robin. >> >> --- a/drivers/iommu/intel/iommu.c >> +++ b/drivers/iommu/intel/iommu.c >> @@ -436,7 +436,7 @@ static int __init intel_iommu_setup(char *str) >>                          pr_warn("intel_iommu=forcedac deprecated; use >> iommu.forcedac instead\n"); >>                          iommu_dma_forcedac = true; >>                  } else if (!strncmp(str, "strict", 6)) { >> -                       pr_info("Disable batched IOTLB flush\n"); >> +                       pr_warn("intel_iommu=strict deprecated; use >> iommu.strict instead\n"); >>                          intel_iommu_strict = 1; >> >> Also update Documentation/admin-guide/kernel-parameters.txt accordingly. > > Thanks, > John