[lkml]   [2017]   [Nov]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 00/23] KAISER: unmap most of the kernel from userspace page tables
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:


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.

 \ /
  Last update: 2017-11-01 23:14    [W:0.195 / U:1.416 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site