Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp2581856yba; Sun, 7 Apr 2019 23:34:38 -0700 (PDT) X-Google-Smtp-Source: APXvYqw9LlwnTzdAataQd9x5z67YfJdmalqA4wPMTOyv/YgwRCUHg9CPBHeq17/5hpBvRQHmiTt3 X-Received: by 2002:a17:902:bc47:: with SMTP id t7mr3291331plz.122.1554705278100; Sun, 07 Apr 2019 23:34:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1554705278; cv=none; d=google.com; s=arc-20160816; b=wHxoevLeHjcwcKAVLp4VLTGFuOw/8vnHH4mwbML6sw11ahi2Rv2CQRc0HjFD6cB81g qAF/UyTn5ukp109+eDgr/uZ8ZGoFbrNihSh2464bFU0h1t7lBR+3hbF3NbALO7wHCQM0 ZvEzKuUXa8ojlqf2QLL5iiyiVV7cISr9TuI2Fx3YHlwxTNboCgPR9WyT1Vi84ZNM/1Bx jRIpjachGCYraaTDpDL/QSfCyKURN3l5+MS5vhFwWxsJLG9rtWJzF/l+5yM1UZ56dKrX 1lNe1XPTOMlV4KUKwmsNMsWPE07IwDQ2E8+5LlwRqiLlk7NCQnVessF9IVHOJkx4RdIJ BShQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date; bh=uc7eRKBVml98KV/NrzJXraxQcuTbB2gohcqynMpuZHk=; b=0jv+Z2JJ50G7CEsHHFcCCSXzPFfPo+JW07zZd4NO2Jl0bum4MD+lfzCFcljSxYp0ce uPmJ/IoQH6XLxqm7M5Ko9RXKvG1Qnj13baNnsdV7vbnPQ80PIwvcra5XhiUFs+Np5VTX xVKbQ8WKiObjBglhSHvynlVZgT1dZFEPN87g4PcJORghq7/7APZ/0YgmBU8G+RLvzwKC WZsA7OfZmN1U1241H7EqlX9b/cHF8We5mjdwNUu4YPNcEnUvOmN8dfjCHYwwpXiyQy4Y I5pxGzI929SbvcW8maOl7gjIPVxp8Dtph4Ia+LCLS7JzuRul5CC2O5oMNGTbDMKKxAPI zelA== 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 v43si9423768pgn.32.2019.04.07.23.34.22; Sun, 07 Apr 2019 23:34:38 -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 S1726494AbfDHGdk (ORCPT + 99 others); Mon, 8 Apr 2019 02:33:40 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:51363 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725881AbfDHGdk (ORCPT ); Mon, 8 Apr 2019 02:33:40 -0400 Received: from p5492ee6e.dip0.t-ipconnect.de ([84.146.238.110] helo=nanos) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1hDNpr-0002VI-W7; Mon, 08 Apr 2019 08:32:52 +0200 Date: Mon, 8 Apr 2019 08:32:50 +0200 (CEST) From: Thomas Gleixner To: "Leizhen (ThunderTown)" 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 Subject: Re: [PATCH v4 0/6] normalize IOMMU dma mode boot options In-Reply-To: <5CAABD03.9000301@huawei.com> Message-ID: References: <20190407124147.13576-1-thunder.leizhen@huawei.com> <5CAABD03.9000301@huawei.com> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. Thanks, tglx