Re: [PATCH] mm/pkeys: generate pkey system call code only if ARCH_HAS_PKEYS is selected

2016-11-14 Thread Dave Hansen
On 11/14/2016 03:12 AM, Heiko Carstens wrote: > Having code for the pkey_mprotect, pkey_alloc and pkey_free system > calls makes only sense if ARCH_HAS_PKEYS is selected. If not selected > these system calls will always return -ENOSPC or -EINVAL. > > To simplify things and have less code generate

Re: [PATCH] mm/pkeys: generate pkey system call code only if ARCH_HAS_PKEYS is selected

2016-11-14 Thread Dave Hansen
On 11/14/2016 03:12 AM, Heiko Carstens wrote: > Having code for the pkey_mprotect, pkey_alloc and pkey_free system > calls makes only sense if ARCH_HAS_PKEYS is selected. If not selected > these system calls will always return -ENOSPC or -EINVAL. > > To simplify things and have less code generate

[PATCH] mm/pkeys: generate pkey system call code only if ARCH_HAS_PKEYS is selected

2016-11-14 Thread Heiko Carstens
Having code for the pkey_mprotect, pkey_alloc and pkey_free system calls makes only sense if ARCH_HAS_PKEYS is selected. If not selected these system calls will always return -ENOSPC or -EINVAL. To simplify things and have less code generate the pkey system call code only if ARCH_HAS_PKEYS is

[PATCH] mm/pkeys: generate pkey system call code only if ARCH_HAS_PKEYS is selected

2016-11-14 Thread Heiko Carstens
Having code for the pkey_mprotect, pkey_alloc and pkey_free system calls makes only sense if ARCH_HAS_PKEYS is selected. If not selected these system calls will always return -ENOSPC or -EINVAL. To simplify things and have less code generate the pkey system call code only if ARCH_HAS_PKEYS is