Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965161AbeALTV3 (ORCPT + 1 other); Fri, 12 Jan 2018 14:21:29 -0500 Received: from one.firstfloor.org ([193.170.194.197]:44792 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964998AbeALTV2 (ORCPT ); Fri, 12 Jan 2018 14:21:28 -0500 Date: Fri, 12 Jan 2018 11:21:26 -0800 From: Andi Kleen To: David Woodhouse Cc: Andi Kleen , tglx@linutronix.de, x86@kernel.org, linux-kernel@vger.kernel.org, pjt@google.com, torvalds@linux-foundation.org, gregkh@linux-foundation.org, peterz@infradead.org, luto@amacapital.net, thomas.lendacky@amd.com, arjan.van.de.ven@intel.com Subject: Re: Improve retpoline for Skylake Message-ID: <20180112192126.su2evwfefdfeaa6g@two.firstfloor.org> References: <20180112184550.6573-1-andi@firstfloor.org> <1515784373.22302.492.camel@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1515784373.22302.492.camel@infradead.org> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: > > Skylake still loses if it takes an SMI, right? SMMs are usually rare, especially on servers, and are usually not very predictible, and even if you have one it would need to interrupt on a quite narrow window, so difficult to arrange. I don't worry about SMM. > Or encounters a call > stack of more than 16 in depth? Yes that's it. This could be mitigated over time. -Andi