On Thu, Aug 27, 2015 at 06:56:49PM +0100, Mathieu Desnoyers wrote: > arm64 sys_membarrier number is already wired for arm64 through > asm-generic/unistd.h, but needs to be allocated separately for > the 32-bit compability layer of arm64. > > [ Untested on this architecture. To try it out: fetch linux-next/akpm, > apply this patch, build/run a membarrier-enabled kernel, and do make > kselftest. ] > > Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx> > CC: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> > CC: linux-api@xxxxxxxxxxxxxxx > CC: Catalin Marinas <catalin.marinas@xxxxxxx> > CC: Will Deacon <will.deacon@xxxxxxx> > --- > arch/arm64/include/asm/unistd32.h | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/arch/arm64/include/asm/unistd32.h b/arch/arm64/include/asm/unistd32.h > index cef934a..d97be80 100644 > --- a/arch/arm64/include/asm/unistd32.h > +++ b/arch/arm64/include/asm/unistd32.h > @@ -797,3 +797,5 @@ __SYSCALL(__NR_memfd_create, sys_memfd_create) > __SYSCALL(__NR_bpf, sys_bpf) > #define __NR_execveat 387 > __SYSCALL(__NR_execveat, compat_sys_execveat) > +#define __NR_membarrier 388 > +__SYSCALL(__NR_membarrier, sys_membarrier) I think people have made similar comments for other architectures, but please also updated __NR_compat_syscalls when adding new compat syscalls here. Will -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
