Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp294355imu; Tue, 27 Nov 2018 12:31:44 -0800 (PST) X-Google-Smtp-Source: AFSGD/UrEAeXNodYP7LYaFuUobs91OWW85bOeMInTMSZ2WaEYio1laDdZID6fU9sjb1CzsVg4Sun X-Received: by 2002:a17:902:7882:: with SMTP id q2mr34900630pll.305.1543350704869; Tue, 27 Nov 2018 12:31:44 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1543350704; cv=none; d=google.com; s=arc-20160816; b=aEXDwNdoAzDUrQ4v0a8d9xdP1mfTLgV6eI3s8KJ+SGVyPOCpBp2m1KZLyAeuRk4xqL vm81EN4+3h9UPWjrAxmQEFNQBlRjQQ5m11nQh9dw0v0ISbV71QRkmicDxJslFiah1taI jwYlZ3lGmjS+JyPPR27OvduvpIVdLy9wkdzkhR+BbsPU+6T7OPKy/Y7wwc3FooaHuMsc CUnT9C5F/t8U/MiN+GrcXNQ3b75i5Yz7Vcb/RgrGPp3HP5Y62GSB5vDYLzseblKjs5ej fwiK1UUl7Yh2Ej6d5IigOZUmrS5udLy/P4kObNOe3Wjipk3Ql91Mh9WoCVTKMfpeEnHX AP8Q== 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=gY2XUh0JBogD7mc8HYyKspfXTC4RzM8Kqz35jkW2sCc=; b=uR/ibVdsigMKKlGMGcVzDIJQzMexyM4umJ05U+D5QhEJdhO8xe0NdH381S6wmSn7eL lGmwQEzrLR8noTQSj1EKygUAcbC9vPkvA4ed/gdK0UkHUkT63oQZz/dDqJqaurs1efLM YPEJCcLtqgV/0HXrD4KFfEB58pzafniGEIgCYBucWFbS7Vi4ksf85Cg1YjWuKOg0eiHY NWp9/z8RLbWVfp3ZJB2w60TXB0+aPGBnwulBDY437TpakB6aRBbHTEduo/YDK6H5uRQT 1zGk4Uu9zOe6gsSjUaKN4pPyJMxK059Mkn5XVVZWdmFpY2KHAutsUD3dl/kc9dMv9uhj 6HAQ== 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 j11si4762473plb.253.2018.11.27.12.31.29; Tue, 27 Nov 2018 12:31:44 -0800 (PST) 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 S1726422AbeK1H34 (ORCPT + 99 others); Wed, 28 Nov 2018 02:29:56 -0500 Received: from Galois.linutronix.de ([146.0.238.70]:58262 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726068AbeK1H34 (ORCPT ); Wed, 28 Nov 2018 02:29:56 -0500 Received: from p4fea46ac.dip0.t-ipconnect.de ([79.234.70.172] helo=nanos) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1gRk0I-0002aP-VR; Tue, 27 Nov 2018 21:30:43 +0100 Date: Tue, 27 Nov 2018 21:30:29 +0100 (CET) From: Thomas Gleixner To: "Lendacky, Thomas" cc: LKML , "x86@kernel.org" , Peter Zijlstra , Andy Lutomirski , Linus Torvalds , Jiri Kosina , Josh Poimboeuf , Andrea Arcangeli , David Woodhouse , Tim Chen , Andi Kleen , Dave Hansen , Casey Schaufler , Asit Mallick , Arjan van de Ven , Jon Masters , Waiman Long , Greg KH , Dave Stewart , Kees Cook Subject: Re: [patch V2 24/28] x86/speculation: Prepare arch_smt_update() for PRCTL mode In-Reply-To: <070bd6a5-fd27-2b6d-efea-6d883ba1f8ec@amd.com> Message-ID: References: <20181125183328.318175777@linutronix.de> <20181125185005.759457117@linutronix.de> <070bd6a5-fd27-2b6d-efea-6d883ba1f8ec@amd.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 Tue, 27 Nov 2018, Lendacky, Thomas wrote: > On 11/25/2018 12:33 PM, Thomas Gleixner wrote: > > +/* Update x86_spec_ctrl_base in case SMT state changed. */ > > +static void update_stibp_strict(void) > > { > > - wrmsrl(MSR_IA32_SPEC_CTRL, x86_spec_ctrl_base); > > + u64 mask = x86_spec_ctrl_base & ~SPEC_CTRL_STIBP; > > + > > + if (sched_smt_active()) > > + mask |= SPEC_CTRL_STIBP; > > + > > + if (mask == x86_spec_ctrl_base) > > + return; > > + > > + pr_info("Spectre v2 user space SMT mitigation: STIBP %s\n", > > + mask & SPEC_CTRL_STIBP ? "always-on" : "off"); > > + x86_spec_ctrl_base = mask; > > + on_each_cpu(update_stibp_msr, NULL, 1); > > Some more testing using spectre_v2_user=on and I've found that during boot > up, once the first SMT thread is encountered no more updates to MSRs for > STIBP are done for any CPUs brought up after that. The first SMT thread > will cause mask != x86_spec_ctrl_base, but then x86_spec_ctrl_base is set > to mask and the check always causes a return for subsequent CPUs that are > brought up. The above code merily handles the switch between SMT and non-SMT mode, because there all other online CPUs need to be updated, but after that each upcoming CPU calls x86_spec_ctrl_setup_ap() which will write the MSR. So it's all good. Thanks, tglx