From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755660AbdKBIEE (ORCPT ); Thu, 2 Nov 2017 04:04:04 -0400 Received: from merlin.infradead.org ([205.233.59.134]:51648 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755576AbdKBID6 (ORCPT ); Thu, 2 Nov 2017 04:03:58 -0400 Date: Thu, 2 Nov 2017 09:03:45 +0100 From: Peter Zijlstra To: Dave Hansen Cc: Ingo Molnar , linux-kernel@vger.kernel.org, linux-mm@kvack.org, Andy Lutomirski , Linus Torvalds , Thomas Gleixner , "H. Peter Anvin" , borisBrian Gerst , Denys Vlasenko , Josh Poimboeuf , Thomas Garnier , Kees Cook Subject: Re: [PATCH 00/23] KAISER: unmap most of the kernel from userspace page tables Message-ID: <20171102080345.x2zceqtrad35bmh3@hirez.programming.kicks-ass.net> References: <20171031223146.6B47C861@viggo.jf.intel.com> <20171101085424.cwvc4nrrdhvjc3su@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Nov 01, 2017 at 03:14:11PM -0700, Dave Hansen wrote: > On 11/01/2017 01:54 AM, Ingo Molnar wrote: > > Beyond the inevitable cavalcade of (solvable) problems that will pop up during > > review, one major item I'd like to see addressed is runtime configurability: it > > should be possible to switch between a CR3-flushing and a regular syscall and page > > table model on the admin level, without restarting the kernel and apps. Distros > > really, really don't want to double the number of kernel variants they have. > > > > The 'Kaiser off' runtime switch doesn't have to be as efficient as > > CONFIG_KAISER=n, at least initialloy, but at minimum it should avoid the most > > expensive page table switching paths in the syscall entry codepaths. > > Due to popular demand, I went and implemented this today. It's not the > prettiest code I ever wrote, but it's pretty small. > > Just in case anyone wants to play with it, I threw a snapshot of it up here: > > > https://git.kernel.org/pub/scm/linux/kernel/git/daveh/x86-kaiser.git/log/?h=kaiser-dynamic-414rc6-20171101 > > I ran some quick tests. When CONFIG_KAISER=y, but "echo 0 > > kaiser-enabled", the tests that I ran were within the noise vs. a > vanilla kernel, and that's with *zero* optimization. I resent you don't think the NMI is performance critical ;-)