Re: [PATCH 17/23] x86/fpu: Eager switch PKRU state

2018-11-19 Thread Sebastian Andrzej Siewior
On 2018-11-08 12:12:52 [+0100], Paolo Bonzini wrote: > On 07/11/2018 20:48, Sebastian Andrzej Siewior wrote: > > index 375226055a413..5b33985d9f475 100644 > > --- a/arch/x86/kernel/fpu/xstate.c > > +++ b/arch/x86/kernel/fpu/xstate.c > > @@ -811,7 +811,7 @@ void fpu__resume_cpu(void) > > * > >

Re: [PATCH 17/23] x86/fpu: Eager switch PKRU state

2018-11-19 Thread Sebastian Andrzej Siewior
On 2018-11-08 12:12:52 [+0100], Paolo Bonzini wrote: > On 07/11/2018 20:48, Sebastian Andrzej Siewior wrote: > > index 375226055a413..5b33985d9f475 100644 > > --- a/arch/x86/kernel/fpu/xstate.c > > +++ b/arch/x86/kernel/fpu/xstate.c > > @@ -811,7 +811,7 @@ void fpu__resume_cpu(void) > > * > >

Re: [PATCH 17/23] x86/fpu: Eager switch PKRU state

2018-11-08 Thread Paolo Bonzini
On 07/11/2018 20:48, Sebastian Andrzej Siewior wrote: > index 375226055a413..5b33985d9f475 100644 > --- a/arch/x86/kernel/fpu/xstate.c > +++ b/arch/x86/kernel/fpu/xstate.c > @@ -811,7 +811,7 @@ void fpu__resume_cpu(void) > * > * Note: does not work for compacted buffers. > */ The comment is

Re: [PATCH 17/23] x86/fpu: Eager switch PKRU state

2018-11-08 Thread Paolo Bonzini
On 07/11/2018 20:48, Sebastian Andrzej Siewior wrote: > index 375226055a413..5b33985d9f475 100644 > --- a/arch/x86/kernel/fpu/xstate.c > +++ b/arch/x86/kernel/fpu/xstate.c > @@ -811,7 +811,7 @@ void fpu__resume_cpu(void) > * > * Note: does not work for compacted buffers. > */ The comment is

[PATCH 17/23] x86/fpu: Eager switch PKRU state

2018-11-07 Thread Sebastian Andrzej Siewior
From: Rik van Riel While most of a task's FPU state is only needed in user space, the protection keys need to be in place immediately after a context switch. The reason is that any access to userspace memory while running in kernel mode also need to abide by the memory permissions specified in

[PATCH 17/23] x86/fpu: Eager switch PKRU state

2018-11-07 Thread Sebastian Andrzej Siewior
From: Rik van Riel While most of a task's FPU state is only needed in user space, the protection keys need to be in place immediately after a context switch. The reason is that any access to userspace memory while running in kernel mode also need to abide by the memory permissions specified in