Received: by 10.223.185.116 with SMTP id b49csp343599wrg; Mon, 19 Feb 2018 23:45:13 -0800 (PST) X-Google-Smtp-Source: AH8x225wfOCa5W5Rh4NHUcyejrM3IK/pYbFNJo04q8H/uVh3Y5D9jcqSBYcD+I1hUPG86g2nBJ1J X-Received: by 10.98.80.89 with SMTP id e86mr16990032pfb.46.1519112713658; Mon, 19 Feb 2018 23:45:13 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519112713; cv=none; d=google.com; s=arc-20160816; b=QWxzRTR9qPnTWLadytEF1pJy4fdv68Gwu/H+a/CojYu+yo6qa0RDTtu+ZBj9ZCG1FF WB8HTECN//hO+Ilokr8GsSA5ATeko5Lr2gobFOyrJW7Vw09i2k2DcFeIG4mBpc3zjRCt MQeyP59htE5FRxP+1NM/FlBq0Rx/w9yey3m7rhe8khQBcvooFydTMlbhTtcxRaYfgQF6 4lztThG4AYOUL2dSJUd8zrDxoNqq+xNaikm54Vc6o26yoJ64OyhHe5dEiDX30fIrHN9u qBvxk2+10JgoRLnSF4v/tvINTOoKuzE52es84wjoxRr08km9IVfng7eWOu6N1hro5Y1D IHMg== 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 :arc-authentication-results; bh=PBIwnlAKCTr8wIQZNhIYiPzOOz06LLDV2FrfHHNlAaM=; b=sQUXm5sGui2VFFu22tmJrzQEmAemdkWZInwyZcPGHvl2yGTDOL+GGOss2PTPv679Ej 6W1GT6L+clSrbEDNdRHzblL5v+6/qzy9f9hmpjQgpQ+G6A5+RvxqxiOdgJ5KCnlBtcOb MlS6Ang0s+qM+o3mgCBEUEthJ+HR7X2PIwW3EUzu+i0JtHQZGLsj5DpN0rX+r7dMXcY5 dVCSgNoV588BRJremzBgXdlqyfPtJA2qRI3A3FJQaM1KMSYQcZGXw0K9QJam6dcWbauS TFL74aZMi3kYdTCXnmudcdsT3Ts1H1eC+L/UQNuXBXek2MdhEjkbp/I0DX0SWFjDMIoQ xwGw== 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 s2si678106pgo.23.2018.02.19.23.44.59; Mon, 19 Feb 2018 23:45:13 -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 S1751348AbeBTHoQ (ORCPT + 99 others); Tue, 20 Feb 2018 02:44:16 -0500 Received: from Galois.linutronix.de ([146.0.238.70]:60674 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750985AbeBTHoP (ORCPT ); Tue, 20 Feb 2018 02:44:15 -0500 Received: from [37.80.9.43] by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1eo2Xd-0000zN-Da; Tue, 20 Feb 2018 08:40:45 +0100 Date: Tue, 20 Feb 2018 08:44:15 +0100 (CET) From: Thomas Gleixner To: David Woodhouse cc: karahmed@amazon.de, x86@kernel.org, kvm@vger.kernel.org, torvalds@linux-foundation.org, pbonzini@redhat.com, linux-kernel@vger.kernel.org, bp@alien8.de, peterz@infradead.org, jmattson@google.com, rkrcmar@redhat.com, arjan.van.de.ven@intel.com, dave.hansen@intel.com, mingo@kernel.org Subject: Re: [PATCH v3 1/4] x86/speculation: Use IBRS if available before calling into firmware In-Reply-To: <1519037457-7643-2-git-send-email-dwmw@amazon.co.uk> Message-ID: References: <1519037457-7643-1-git-send-email-dwmw@amazon.co.uk> <1519037457-7643-2-git-send-email-dwmw@amazon.co.uk> 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, 19 Feb 2018, David Woodhouse wrote: > Retpoline means the kernel is safe because it has no indirect branches. > But firmware isn't, so use IBRS for firmware calls if it's available. > > Block preemption while IBRS is set, although in practice the call sites > already had to be doing that. > > Ignore hpwdt.c for now. It's taking spinlocks and calling into firmware > code, from an NMI handler. I don't want to touch that with a bargepole. > > Signed-off-by: David Woodhouse Reviewed-by: Thomas Gleixner