Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp2703064yba; Mon, 8 Apr 2019 02:53:35 -0700 (PDT) X-Google-Smtp-Source: APXvYqySEbpgq539jQgAyTdcJo5g+M2rJ3x4tNzR29msJ+40Lfp2OJ3OLVlAcDyBVW/V17nQD0Jm X-Received: by 2002:a62:1881:: with SMTP id 123mr28827792pfy.25.1554717215418; Mon, 08 Apr 2019 02:53:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1554717215; cv=none; d=google.com; s=arc-20160816; b=Ygp6F9owMvXLu71ZFrkM6+GSCJlTpDh5kFRPOKcrf8EeqSPMz6DtFEdL9JC+hWflMe xx7zT32pAv764ISoyqOOSeMuCxxJahJEgp+tOP/DDeihDpQMcKuaFPmpfRmn7aIGk71A H3G4kVIz3qgdRDtzZhady4i/1hU46GjJ6Yylt//x72oWH/AUb5QbEYX8PY57ZnePViei sUCl8Om7eTwF6sEq6xCHGV1+ElUa5TFa5oHqMfNuDpWZXSe25qM5ulXA5nwCU08jcSv8 o1/bfa7jUUsluxQHVwogIzLrizX1PU7hM+DIq9jmAIaXBAxGokoc0LQyeHWv2wLVRg0g ZETw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:in-reply-to :mime-version:user-agent:date:message-id:from:cc:references:to :subject; bh=F3GlkkKtZhHzRAovVsW6fQK0Whvuf3KuMF+O7yQf0Eg=; b=JpLDoVWPXjCXzL1nJG3VMYRqLdqAzJmZjVi+5DJ6bXMRbBx4O9eKn5VWhq3lqXz2ib Br5H8Rs38uu1QiszRE0qOLjYXd1sBP/hcb+nHwuWdncvOZ7P4/mDmV3Rtk1zNOhLOBSv T3RmQS1qxVgGxsDV0K5voTwvtQ66QVendlyRHdo8FzjtF2Cr6k94LkInNr8eyCmhst39 asDqGXe1LmzjOrfNszaviBxSRY53r+irzyGXGaso7VN6GVIU8A7ey9UD3C8zN1KTYdes DwuhmHLmF4C9tf5kMbjIpoSsWKssQfVvlAoQWwi6vrC8saqszieDevB0E1RlIBvF29s+ IAPA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q1si23034313pgh.396.2019.04.08.02.53.19; Mon, 08 Apr 2019 02:53:35 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726579AbfDHJwJ (ORCPT + 99 others); Mon, 8 Apr 2019 05:52:09 -0400 Received: from szxga05-in.huawei.com ([45.249.212.191]:6707 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725933AbfDHJwJ (ORCPT ); Mon, 8 Apr 2019 05:52:09 -0400 Received: from DGGEMS405-HUB.china.huawei.com (unknown [172.30.72.58]) by Forcepoint Email with ESMTP id 633868A0D550D054A9A4; Mon, 8 Apr 2019 17:52:06 +0800 (CST) Received: from [127.0.0.1] (10.177.23.164) by DGGEMS405-HUB.china.huawei.com (10.3.19.205) with Microsoft SMTP Server id 14.3.408.0; Mon, 8 Apr 2019 17:51:59 +0800 Subject: Re: [PATCH v4 0/6] normalize IOMMU dma mode boot options To: Thomas Gleixner References: <20190407124147.13576-1-thunder.leizhen@huawei.com> <5CAABD03.9000301@huawei.com> CC: Hanjun Guo , Jean-Philippe Brucker , John Garry , "Robin Murphy" , Will Deacon , "Joerg Roedel" , Jonathan Corbet , linux-doc , Sebastian Ott , "Gerald Schaefer" , Martin Schwidefsky , Heiko Carstens , Benjamin Herrenschmidt , Paul Mackerras , Michael Ellerman , Tony Luck , Fenghua Yu , Ingo Molnar , Borislav Petkov , "H . Peter Anvin" , David Woodhouse , iommu , linux-kernel , linux-s390 , linuxppc-dev , x86 , linux-ia64 From: "Leizhen (ThunderTown)" Message-ID: <5CAB19BC.2040804@huawei.com> Date: Mon, 8 Apr 2019 17:51:56 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.177.23.164] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2019/4/8 14:32, Thomas Gleixner wrote: > On Mon, 8 Apr 2019, Leizhen (ThunderTown) wrote: >>> >>> This will break systems using boot options as now, and I think >>> this is unacceptable. If you want to do so, just introduce iommu.dma_mode >>> on top of those iommu boot options with dma mode boot options unchanged, >>> and iommu.dma_mode is for all archs but compatible with them. >> >> I just changed the boot options name, but keep the function no change. I added >> all related maintainers/supporters in the "to=" list, maybe we can disuss this. > > Changing the name _IS_ the problem. Think about unattended updates. > >> Should I add some "obsoleted" warnings for old options and keep them for a while? > > No, just keep the old options around for backwards compatibilty sake. We > just do not add new arch specific options in the future. New options need > to use the generic iommu.dma_mode name space. OK, thanks for your advise. > > Thanks, > > tglx > > . > -- Thanks! BestRegards