Speaking of pages and slowdowns,
is there a better place to ask this question:

>From "'Turning Tables' shared page tables vuln":

"""
'New "Turning Tables" Technique Bypasses All Windows Kernel Mitigations'
https://www.bleepingcomputer.com/news/security/new-turning-tables-technique-bypasses-all-windows-kernel-mitigations/

> Furthermore, since the concept of page tables is also used by Apple and
the Linux project, macOS and Linux are, in theory, also vulnerable to this
technique, albeit the researchers have not verified such attacks, as of yet.

Slides:
https://cdn2.hubspot.net/hubfs/487909/Turning%20(Page)%20Tables_Slides.pdf

Naturally, I took notice and decided to forward the latest scary headline
to this list to see if this is already being addressed?
"""

On Saturday, September 1, 2018, Linus Torvalds <
torvalds@linux-foundation.org> wrote:

> On Fri, Aug 31, 2018 at 12:45 AM Julian Stecklina <jsteckli@amazon.de>
> wrote:
> >
> > I've been spending some cycles on the XPFO patch set this week. For the
> > patch set as it was posted for v4.13, the performance overhead of
> > compiling a Linux kernel is ~40% on x86_64[1]. The overhead comes almost
> > completely from TLB flushing. If we can live with stale TLB entries
> > allowing temporary access (which I think is reasonable), we can remove
> > all TLB flushing (on x86). This reduces the overhead to 2-3% for
> > kernel compile.
>
> I have to say, even 2-3% for a kernel compile sounds absolutely horrendous.
>
> Kernel bullds are 90% user space at least for me, so a 2-3% slowdown
> from a kernel is not some small unnoticeable thing.
>
>            Linus
>