[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190408200331.wvvt4izcasmotkp6@linutronix.de>
Date: Mon, 8 Apr 2019 22:03:31 +0200
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Dave Hansen <dave.hansen@...el.com>
Cc: linux-kernel@...r.kernel.org, x86@...nel.org,
Andy Lutomirski <luto@...nel.org>,
Paolo Bonzini <pbonzini@...hat.com>,
Radim Krčmář <rkrcmar@...hat.com>,
kvm@...r.kernel.org, "Jason A. Donenfeld" <Jason@...c4.com>,
Rik van Riel <riel@...riel.com>,
Dave Hansen <dave.hansen@...ux.intel.com>
Subject: Re: [PATCH 19/27] x86/fpu: Update xstate's PKRU value on write_pkru()
On 2019-04-08 11:14:28 [-0700], Dave Hansen wrote:
> On 4/3/19 9:41 AM, Sebastian Andrzej Siewior wrote:
> > During the context switch the xstate is loaded which also includes the
> > PKRU value.
> > If xstate is restored on return to userland it is required that the
> > PKRU value in xstate is the same as the one in the CPU.
>
> All of the protection keys bits in here look ok to me. Thanks for the
> sustained work to get all those into shape. I know it's a special
> snowflake.
> Although I paid much closer attention to the PK bits, feel free to add:
>
> Reviewed-by: Dave Hansen <dave.hansen@...el.com>
>
> for the series.
Thank you.
Sebastian
Powered by blists - more mailing lists