Hello Bharata, On Tue, Aug 11, 2015 at 03:37:29PM +0530, Bharata B Rao wrote: > May be it is a bit late to bring this up, but I needed the following fix > to userfault21 branch of your git tree to compile on powerpc. Not late, just in time. I increased the number of syscalls in earlier versions, it must have gotten lost during a rejecting rebase, sorry. I applied it to my tree and it can be applied to -mm and linux-next, thanks! The syscall for arm32 are also ready and on their way to the arm tree, the testsuite worked fine there. ppc also should work fine if you could confirm it'd be interesting, just beware that I got a typo in the testcase: diff --git a/tools/testing/selftests/vm/userfaultfd.c b/tools/testing/selftests/vm/userfaultfd.c index 76071b1..925c3c9 100644 --- a/tools/testing/selftests/vm/userfaultfd.c +++ b/tools/testing/selftests/vm/userfaultfd.c @@ -70,7 +70,7 @@ #define __NR_userfaultfd 323 #elif defined(__i386__) #define __NR_userfaultfd 374 -#elif defined(__powewrpc__) +#elif defined(__powerpc__) #define __NR_userfaultfd 364 #else #error "missing __NR_userfaultfd definition" > ---- > > powerpc: Bump up __NR_syscalls to account for __NR_userfaultfd > > From: Bharata B Rao <bharata@xxxxxxxxxxxxxxxxxx> > > With userfaultfd syscall, the number of syscalls will be 365 on PowerPC. > Reflect the same in __NR_syscalls. > > Signed-off-by: Bharata B Rao <bharata@xxxxxxxxxxxxxxxxxx> > --- > arch/powerpc/include/asm/unistd.h | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/arch/powerpc/include/asm/unistd.h b/arch/powerpc/include/asm/unistd.h > index f4f8b66..4a055b6 100644 > --- a/arch/powerpc/include/asm/unistd.h > +++ b/arch/powerpc/include/asm/unistd.h > @@ -12,7 +12,7 @@ > #include <uapi/asm/unistd.h> > > > -#define __NR_syscalls 364 > +#define __NR_syscalls 365 > > #define __NR__exit __NR_exit > #define NR_syscalls __NR_syscalls Reviewed-by: Andrea Arcangeli <aarcange@xxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html