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.5 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 BAF98C6783B for ; Tue, 11 Dec 2018 21:19:54 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 7735E20851 for ; Tue, 11 Dec 2018 21:19:54 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=alien8.de header.i=@alien8.de header.b="H2nlhSRB" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 7735E20851 Authentication-Results: mail.kernel.org; dmarc=fail (p=reject dis=none) header.from=alien8.de Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726315AbeLKVTx (ORCPT ); Tue, 11 Dec 2018 16:19:53 -0500 Received: from mail.skyhub.de ([5.9.137.197]:37362 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726136AbeLKVTx (ORCPT ); Tue, 11 Dec 2018 16:19:53 -0500 Received: from zn.tnic (p200300EC2BCD2B0010F6E1EC68D6BA6C.dip0.t-ipconnect.de [IPv6:2003:ec:2bcd:2b00:10f6:e1ec:68d6:ba6c]) (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 011A71EC028C; Tue, 11 Dec 2018 22:19:51 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1544563192; 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=HDw6+0CtQh6zTBCYZ77G6/eUIzMvWFHPFTZNV9Tmoyw=; b=H2nlhSRBf15m1AY2iNL6x7QuCd7DKNm+8kZBwVVLWz8TuWeXi7TrI4wDI54cKvrRsZrXsy WQV3/1xo2bwJs3K2+bv68bPcyKevvjOoLKkfrPOXej/ikCbjXFQn90Z0OhPY3NJOEsNHOv mdAlE0Xd1/Pty9AA/4vWmVcblI1YB8k= Date: Tue, 11 Dec 2018 22:19:44 +0100 From: Borislav Petkov To: "Lendacky, Thomas" Cc: "x86@kernel.org" , "linux-kernel@vger.kernel.org" , Andrea Arcangeli , Konrad Rzeszutek Wilk , Jiri Kosina , Ingo Molnar , Thomas Gleixner , Tim Chen , David Woodhouse Subject: Re: [PATCH] x86/speculation: Add support for STIBP always-on preferred mode Message-ID: <20181211211944.GT27375@zn.tnic> References: <20181211190959.28321.56433.stgit@tlendack-t1.amdoffice.net> <3308b5d2-0c59-fa33-472b-f56633d39575@amd.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <3308b5d2-0c59-fa33-472b-f56633d39575@amd.com> 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 On Tue, Dec 11, 2018 at 07:19:09PM +0000, Lendacky, Thomas wrote: > Alternatively, I can reuse SPECTRE_V2_USER_STRICT and issue pr_info_once() > to show that the method has been switched. This would reduce the changes > to the code, but then the sysfs information doesn't show the switch (which > may be just fine). You can still query X86_FEATURE_AMD_STIBP_ALWAYS_ON in stibp_state(), no? But yeah, forcing SPECTRE_V2_USER_STRICT on STIBP_ALWAYS_ON makes sense to me, with the already gazillion options we have :-\ -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.