Re: [PATCH 23/43] x86/mm/kaiser: Introduce user-mapped per-cpu areas

2017-11-27 Thread Dave Hansen
On 11/26/2017 09:41 AM, Borislav Petkov wrote: >> The KAISER approach keeps two copies of the page tables: one for running >> in the kernel and one for running userspace. But, there are a few >> structures that are needed for switching in and out of the kernel and >> a good subset of *those* are p

Re: [PATCH 23/43] x86/mm/kaiser: Introduce user-mapped per-cpu areas

2017-11-27 Thread Ingo Molnar
* Borislav Petkov wrote: > On Fri, Nov 24, 2017 at 06:23:51PM +0100, Ingo Molnar wrote: > > From: Dave Hansen > > > > These patches are based on work from a team at Graz University of > > Technology posted here: https://github.com/IAIK/KAISER > > > > The KAISER approach keeps two copies of th

Re: [PATCH 23/43] x86/mm/kaiser: Introduce user-mapped per-cpu areas

2017-11-26 Thread Borislav Petkov
On Fri, Nov 24, 2017 at 06:23:51PM +0100, Ingo Molnar wrote: > From: Dave Hansen > > These patches are based on work from a team at Graz University of > Technology posted here: https://github.com/IAIK/KAISER > > The KAISER approach keeps two copies of the page tables: one for running > in the ke

[PATCH 23/43] x86/mm/kaiser: Introduce user-mapped per-cpu areas

2017-11-24 Thread Ingo Molnar
From: Dave Hansen These patches are based on work from a team at Graz University of Technology posted here: https://github.com/IAIK/KAISER The KAISER approach keeps two copies of the page tables: one for running in the kernel and one for running userspace. But, there are a few structures that a

[PATCH 23/43] x86/mm/kaiser: Introduce user-mapped per-cpu areas

2017-11-24 Thread Ingo Molnar
From: Dave Hansen These patches are based on work from a team at Graz University of Technology posted here: https://github.com/IAIK/KAISER The KAISER approach keeps two copies of the page tables: one for running in the kernel and one for running userspace. But, there are a few structures that a