Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp5808514yba; Thu, 11 Apr 2019 06:16:55 -0700 (PDT) X-Google-Smtp-Source: APXvYqy5Pg/Fh7lUst35CCKtFG3BTaP8QDETf6XkPzFhtrCFe5LbV9o+kDF4Z/S3LQck6xCVUrsP X-Received: by 2002:a62:b411:: with SMTP id h17mr31640091pfn.61.1554988614934; Thu, 11 Apr 2019 06:16:54 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1554988614; cv=none; d=google.com; s=arc-20160816; b=YNQzmpxR8Bt733MyMort80yEAQgWmn87qHHkoHftdj1B0ohVjQI7rbA77bFdkImng4 J4qRqQ8YudIMB9CpT7zS9hofNnuY2OGeGJaeB22QP4rjWMFZ/5MoBw44vh1lasgIrmYO f+wPFDnlM6ZeRPpX3I1zHL0BmszbxWl3aaVTSeuEDYLEGKRUjN2Jyz9p2RZNJjuTWKiM RVFsMsW778PJ0zXaH98ny1D4wUVASJDR6mSvk0HuRlMMROhabRoOrEXzRaEfZZKjkW0J /pCLx9ueuf48mGg1CAsn+ryTNQd1baxHWySvGfoETr0xGJBKRdnSSKpRO57+0rkLYxXI n6aw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=2Jdpu0lCGy+nM8afb+hoi0kI0AjF9zqlE/MN8tAnyC8=; b=nS3r9THxdbDKg7jE+lIeVQ29h5Kd3JGphU5AVI9gEkEU/DbsJKZbZ8arB8kQ/p30FV daUMcL5SFbx4AxOnz6DwzjB4rudMchQklw/AUpqCQK5/JnrCEWgZQxHjxHsDqDEwsJsL 8RRW42fOcR/xbqsnoiUMmRfyG/JeKc3C7zkZQp7ZULYNbQ03X7IsO4rtbvPnd/CEaxVF J7Hx7WMxlIXPtCRiZF9tWxNQ78hHAXnx/hIeQFHG5VsyL9wuGhW5LjRbbccLK+kQxm00 j+s6fshMruyTsfUmLzQxrPJnjloN0PQ9Uune2q2FHe3haA/LeRl7o1067blvuyBxwprm nLyQ== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f96si12406237plb.267.2019.04.11.06.16.38; Thu, 11 Apr 2019 06:16:54 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726636AbfDKNPs (ORCPT + 99 others); Thu, 11 Apr 2019 09:15:48 -0400 Received: from mx1.redhat.com ([209.132.183.28]:51868 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726145AbfDKNPs (ORCPT ); Thu, 11 Apr 2019 09:15:48 -0400 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id B4BDE30832DE; Thu, 11 Apr 2019 13:15:47 +0000 (UTC) Received: from treble (ovpn-120-231.rdu2.redhat.com [10.10.120.231]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 3AA9061998; Thu, 11 Apr 2019 13:15:42 +0000 (UTC) Date: Thu, 11 Apr 2019 08:15:40 -0500 From: Josh Poimboeuf To: Thomas Gleixner Cc: Michael Ellerman , Borislav Petkov , linux-kernel@vger.kernel.org, x86@kernel.org, Ingo Molnar , "H . Peter Anvin" , Andy Lutomirski , Peter Zijlstra , Jiri Kosina , Waiman Long , Andrea Arcangeli , Jon Masters , Benjamin Herrenschmidt , Paul Mackerras , linuxppc-dev@lists.ozlabs.org, Martin Schwidefsky , Heiko Carstens , linux-s390@vger.kernel.org, Catalin Marinas , Will Deacon , linux-arm-kernel@lists.infradead.org, linux-arch@vger.kernel.org, Greg Kroah-Hartman , Tyler Hicks , Linus Torvalds Subject: Re: [PATCH RFC 1/5] cpu/speculation: Add 'cpu_spec_mitigations=' cmdline options Message-ID: <20190411131540.754t5t4tp55i6vjq@treble> References: <20190405131211.GE23348@zn.tnic> <20190405142048.burthk2jnpcvi2om@treble> <20190405152059.GG23348@zn.tnic> <20190405160136.GI23348@zn.tnic> <20190405161852.nmpk22omgiety4df@treble> <87sguqwgu7.fsf@concordia.ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20180716 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.44]); Thu, 11 Apr 2019 13:15:48 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Apr 10, 2019 at 02:10:01PM +0200, Thomas Gleixner wrote: > On Wed, 10 Apr 2019, Michael Ellerman wrote: > > Josh Poimboeuf writes: > > > > > On Fri, Apr 05, 2019 at 06:01:36PM +0200, Borislav Petkov wrote: > > >> Thinking about this more, we can shave off the first 4 chars and have it > > >> be: > > >> > > >> spec_mitigations= > > >> > > >> I think it is painfully clear which speculation mitigations we mean. And > > >> the other switches don't have "cpu_" prefixes too so... > > > > > > Sure, I'm ok with renaming it to that, if there are no objections. > > > > What about when we have a mitigation for a non-speculation related bug :) > > Those kind of silicon bugs are usually mitigated unconditionally. Right. But at least "mitigations=" is nice and short. We could clarify in the documentation that it doesn't apply to *all* mitigations, only the ones which are optional and which can affect performance. And it would give us the freedom to include any future "optional" mitigations, spec or not. I kind of like it. But I could go either way. -- Josh