From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Hansen Subject: Re: [PATCH 6/9] x86, pkeys: add pkey set/get syscalls Date: Tue, 12 Jul 2016 08:39:07 -0700 Message-ID: <57850F1B.4080306@sr71.net> References: <20160707124719.3F04C882@viggo.jf.intel.com> <20160707124728.C1116BB1@viggo.jf.intel.com> <20160707144508.GZ11498@techsingularity.net> <577E924C.6010406@sr71.net> <20160708071810.GA27457@gmail.com> <577FD587.6050101@sr71.net> <20160709083715.GA29939@gmail.com> <20160711073534.GA19615@gmail.com> <5783AD25.8020303@sr71.net> <20160712071305.GA13444@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20160712071305.GA13444@gmail.com> Sender: linux-arch-owner@vger.kernel.org To: Ingo Molnar Cc: Andy Lutomirski , linux-arch , Thomas Gleixner , "linux-mm@kvack.org" , Mel Gorman , Linus Torvalds , Andrew Morton , Linux API , Arnd Bergmann , "linux-kernel@vger.kernel.org" , Al Viro , Peter Zijlstra , Hugh Dickins , "H. Peter Anvin" , X86 ML , Dave Hansen List-Id: linux-api@vger.kernel.org On 07/12/2016 12:13 AM, Ingo Molnar wrote: >> > Remember, PKRU is just a *bitmap*. The only place keys are stored is in the >> > page tables. > A pkey is an index *and* a protection mask. So by representing it as a bitmask we > lose per thread information. This is what I meant by 'incomplete shadowing' - for > example the debug code couldn't work: if we cleared a pkey in a task we wouldn't > know what to restore it to with the current data structures, right? Right. I actually have some code to do the shadowing that I wrote to explore how to do different PKRU values in signal handlers. The code only shadowed the keys that were currently allocated, and used the (mm-wide) allocation map to figure that out. It did not have a separate per-thread concept of which parts of PKRU need to be shadowed. It essentially populated the shadow value on all pkru_set() calls.