From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8A918C10F0A for ; Fri, 5 Apr 2019 16:01:47 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 5B6AA21852 for ; Fri, 5 Apr 2019 16:01:47 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=alien8.de header.i=@alien8.de header.b="iokLCSUJ" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731469AbfDEQBq (ORCPT ); Fri, 5 Apr 2019 12:01:46 -0400 Received: from mail.skyhub.de ([5.9.137.197]:34274 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726135AbfDEQBp (ORCPT ); Fri, 5 Apr 2019 12:01:45 -0400 Received: from zn.tnic (p200300EC2F148A00329C23FFFEA6A903.dip0.t-ipconnect.de [IPv6:2003:ec:2f14:8a00:329c:23ff:fea6:a903]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id 5B86F1EC05A6; Fri, 5 Apr 2019 18:01:43 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1554480103; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:in-reply-to:in-reply-to: references:references; bh=WiKi+/KybWEvJm3sHhOrb8yL6K6W6lHXXDTfb7hwFlI=; b=iokLCSUJF9eQMIJ4ncEKkI18NERXGhjGQc3uBFWmKzG7RCQIUyWtFNygNMeOjZv/xvBCHs wmL0I7Xk2KSOOQKbSeMOVFpufl2QJyJBqgU6bLr/RhHif+W0a0AlDw6JdDxPRaRmutPBX0 AFJtsWDFzkiUz8pT1Px77+/Y/LTNgaI= Date: Fri, 5 Apr 2019 18:01:36 +0200 From: Borislav Petkov To: Josh Poimboeuf Cc: linux-kernel@vger.kernel.org, x86@kernel.org, Thomas Gleixner , Ingo Molnar , "H . Peter Anvin" , Andy Lutomirski , Peter Zijlstra , Jiri Kosina , Waiman Long , Andrea Arcangeli , Jon Masters , Benjamin Herrenschmidt , Paul Mackerras , Michael Ellerman , 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: <20190405160136.GI23348@zn.tnic> References: <20190405131211.GE23348@zn.tnic> <20190405142048.burthk2jnpcvi2om@treble> <20190405152059.GG23348@zn.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20190405152059.GG23348@zn.tnic> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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... -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.