Received: by 10.223.176.46 with SMTP id f43csp871236wra; Sat, 20 Jan 2018 06:28:20 -0800 (PST) X-Google-Smtp-Source: AH8x226i4X9Xufgv6jZI/oVrHWZPrJpaOmRMLa3u7LAp/g7eHv0En+WR2SxbwRQKOZndPSaJgGWW X-Received: by 2002:a17:902:678e:: with SMTP id g14-v6mr958009plk.309.1516458499897; Sat, 20 Jan 2018 06:28:19 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516458499; cv=none; d=google.com; s=arc-20160816; b=z5VA0bPfs/LI8DZLrB8Kc/RETyJthvA662JM707ZQHihpnezyasDE1RzAqk2k48x0q hgKODoJx+4s6h1x3cSDM+D124YMCGUhybR0WqriQCuPF0eRDV7Y7i91HnJ3Qz5c2SlVV hVA8qaCjHdN238ymT5WdOVzhF/WbZsjiIAXmZa4IAMWAuO51A0wxjj0EYN5iHgf3VxkW KhTLxjqXmX3Se+r07wuHKtF3vHh3MaCPD2y+vdGtAh+bMMf/7+ECwslN60Vd6l8dRURM GjKSGsk5dIzAendMmMKa7dCSxbX/asBiSPBNNyOA3CN0swL7XAQ6DNRQbZ+RDAePo4n1 DiuA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature:arc-authentication-results; bh=eElRrM3srNIggaLxNa8Bcj42KlztsH+UrcB7d2HM00k=; b=iQfZ5VAUFi3vuA0xt8UGkZj3K2zkWUGrKsZ9m77N+wEU4jDa+EERmeeLQjRa2ncADr bRqvG4uCue85PCJ8x4oCUd1IObrJR7i7okg4CGcemvvL1A7pCf643f5MlULqt6HJdUlP DwZXKFZaxqOGnzhtjMYjxaJGx6PDYJOVWHhMSyc88rAbAHAqc3N9vO+ES73XfFPBqReZ FRdfU3MeaJvuAnRJ76wlKGHNfvZazfN4RjTMDGzM6bzldoB2TuMINDIMMmC4iHt/2USk Zl8KxIUbW+hIwzFDv7nsgwF77TL7yYq+Hk5nP/nPTDmsGCC+VVFbGTGuMPvENgfltj3I Q73A== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=QQAXleSN; 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 u26si6443380pge.210.2018.01.20.06.28.06; Sat, 20 Jan 2018 06:28:19 -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; dkim=fail header.i=@gmail.com header.s=20161025 header.b=QQAXleSN; 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 S1756212AbeATO0j (ORCPT + 99 others); Sat, 20 Jan 2018 09:26:39 -0500 Received: from mail-wr0-f177.google.com ([209.85.128.177]:37154 "EHLO mail-wr0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751130AbeATO0b (ORCPT ); Sat, 20 Jan 2018 09:26:31 -0500 Received: by mail-wr0-f177.google.com with SMTP id f11so4064889wre.4 for ; Sat, 20 Jan 2018 06:26:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=eElRrM3srNIggaLxNa8Bcj42KlztsH+UrcB7d2HM00k=; b=QQAXleSNrzhSjgcaasGXAots5wRfbQQNZaGv7YBoOZUN3jOikSN4mON9SjqsTI+44L DfO/43UO6AE5XhmdXubY2Kqa1928iEZZj6zAYnUckmukEld1dZjSDaVclsDl6+SOQcS8 91DQzgKXc76fkzHRIKOpzdXrMeLsPtNRr9BSro5scqkpXNgmYah/FVta9hNeQ8AlN23N bLXa6/KbdvMLK2oTnBt5zdFMZXX9sZJ4gUks669ndN6K00/MiG2mOm+DvOatESW8+j9D xj8xPCCPvN83KyPw85W8qzjQa6yfCXAEpKgKeHlSl9YA6xCMP6dNf+HtNXaSjF5F/8gx AYuw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=eElRrM3srNIggaLxNa8Bcj42KlztsH+UrcB7d2HM00k=; b=NzF1WjWmGlyKT4YlIRxQDorhZSt2XTX+WaHmHsu5peK7Roy/2QBSyNJCAUKgPq2FLP S6oPI9cxyfbpHAPZXyoe3f4rTttvwkLLWfEzfOLJT0g+uF474p9VJz0fH0G8kQpr1SsH Bhksyt7+/0Xa/jbnfa0Af8FT3IG2KHgzJE5r3wW0asJgZ514f0mSj4Yt/ctOfgJVsbrT 2r4D93S+37X6kUXrNlMpAxZOZOw1DAETdLceqMZoZTj4nU41GrxOFi4XAmqgYsfENvyI 3xADNUS5+q1XdYZYtplOZDoCZTVvb1c5AsWHfH+GJGx5luu4+EWbbelOsUvSMQ3vF9vc YjhA== X-Gm-Message-State: AKwxytcwIkn3cLMyE71meGKSxa2rymrg7BK//X2SA/bgm+P34qbttiCp sJCad/bsX8UQAJPBbbF0VFs= X-Received: by 10.223.185.92 with SMTP id b28mr1584687wrg.196.1516458390782; Sat, 20 Jan 2018 06:26:30 -0800 (PST) Received: from gmail.com (2E8B0CD5.catv.pool.telekom.hu. [46.139.12.213]) by smtp.gmail.com with ESMTPSA id 59sm11480482wrs.85.2018.01.20.06.26.29 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sat, 20 Jan 2018 06:26:29 -0800 (PST) Date: Sat, 20 Jan 2018 15:26:27 +0100 From: Ingo Molnar To: Nadav Amit Cc: Dave Hansen , LKML , Andy Lutomirski , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , the arch/x86 maintainers , w@1wt.eu, Linus Torvalds Subject: Re: [RFC] x86: Avoid CR3 load on compatibility mode with PTI Message-ID: <20180120142627.jttjdsenwsedvle6@gmail.com> References: <20180114201306.3554-1-namit@vmware.com> <57a8fa6b-a1d1-d440-ce13-b1d06d265584@linux.intel.com> <3D823F02-89EF-48D9-913D-5E65391F6F9D@gmail.com> <20180116004128.us5uprkzrr5gf4li@gmail.com> <5D6CD440-B20F-4ABF-8B02-EE87205B661D@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5D6CD440-B20F-4ABF-8B02-EE87205B661D@gmail.com> User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Nadav Amit wrote: > > So we are trading a 5-15% slowdown (PTI) for another 5-15% slowdown, plus we > > are losing the soft-SMEP feature on older CPUs that PTI enables, which is a > > pretty powerful mitigation technique. > > This soft-SMEP can be kept by keeping PTI if SMEP is unsupported. Although we > trade slowdowns, they are different ones, which allows the user to make his best > decision. Indeed, not allowing PTI to be disabled if SMEP is unavailable might be a solution. > > Yes, I suspect in some (maybe many) cases it would be a speedup, but I really > > don't like the underlying assumptions and tradeoffs here. (Not that I like any > > of this whole Meltdown debacle TBH.) > > To make sure that I understand correctly - the assumptions are that disabling > PTI on compatibility mode would: (1) Benefit some workloads; (2) Be useful, even > if we only consider CPUs with SMEP; and (3) Secure. > > Under these assumptions, the tradeoff is slightly greater code complexity for > considerably better performance of 32-bit code; in some common cases this makes > 32-bit code to perform significantly better than 64-bit code. > > Am I missing something? My main concern was initially security, but so far from > your aggregated feedback I did not see something concrete which cannot > relatively easily be addressed. Yes, I suppose. Thanks, Ingo