lkml.org 
[lkml]   [2017]   [Jul]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [RFC v5 34/38] procfs: display the protection-key number associated with a vma
    On Mon, Jul 10, 2017 at 08:37:28AM +0530, Anshuman Khandual wrote:
    > On 07/06/2017 02:52 AM, Ram Pai wrote:
    > > Display the pkey number associated with the vma in smaps of a task.
    > > The key will be seen as below:
    > >
    > > ProtectionKey: 0
    > >
    > > Signed-off-by: Ram Pai <linuxram@us.ibm.com>
    > > ---
    > > arch/powerpc/kernel/setup_64.c | 8 ++++++++
    > > 1 files changed, 8 insertions(+), 0 deletions(-)
    > >
    > > diff --git a/arch/powerpc/kernel/setup_64.c b/arch/powerpc/kernel/setup_64.c
    > > index f35ff9d..ebc82b3 100644
    > > --- a/arch/powerpc/kernel/setup_64.c
    > > +++ b/arch/powerpc/kernel/setup_64.c
    > > @@ -37,6 +37,7 @@
    > > #include <linux/memblock.h>
    > > #include <linux/memory.h>
    > > #include <linux/nmi.h>
    > > +#include <linux/pkeys.h>
    > >
    > > #include <asm/io.h>
    > > #include <asm/kdump.h>
    > > @@ -745,3 +746,10 @@ static int __init disable_hardlockup_detector(void)
    > > }
    > > early_initcall(disable_hardlockup_detector);
    > > #endif
    > > +
    > > +#ifdef CONFIG_PPC64_MEMORY_PROTECTION_KEYS
    >
    > Why not for X86 protection keys ?

    hmm.. I dont understand the comment.


    --
    Ram Pai

    \
     
     \ /
      Last update: 2017-07-10 08:02    [W:3.867 / U:0.004 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site