On Tue, Jul 11, 2017 at 10:33:09AM -0700, Dave Hansen wrote: > On 07/05/2017 02:22 PM, Ram Pai wrote: > > Abstracted out the arch specific code into the header file, and > > added powerpc specific changes. > > > > a) added 4k-backed hpte, memory allocator, powerpc specific. > > b) added three test case where the key is associated after the page is > > accessed/allocated/mapped. > > c) cleaned up the code to make checkpatch.pl happy > > There's a *lot* of churn here. If it breaks, I'm going to have a heck > of a time figuring out which hunk broke. Is there any way to break this > up into a series of things that we have a chance at bisecting? Just finished breaking down the changes into 20 gradual increments. I have pushed it to my github tree at https://github.com/rampai/memorykeys.git branch is memkey.v6-rc3 See if it works for you. I am sure I would have broken something on x86 since I dont have a x86 platform to test. Let me know, Thanks, RP -- To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
