Re: [RFC PATCH v2 6/9] arm: allocate sys_membarrier system call number
From: Mathieu Desnoyers <hidden>
Date: 2015-09-17 13:38:06
Also in:
lkml
----- On Sep 17, 2015, at 9:13 AM, Russell King - ARM Linux linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org wrote:
On Wed, Sep 16, 2015 at 06:27:10PM +0000, Mathieu Desnoyers wrote:quoted
----- On Sep 7, 2015, at 12:15 PM, Mathieu Desnoyers mathieu.desnoyers-vg+e7yoeK/dWk0Htik3J/w@public.gmane.org wrote:quoted
[ 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. ]Hi, We tested the system call on our ARM board (Wandboard, SoC Freescale i.MX6 Quad) by applying this patch on top of Linux 4.3-rc1. Both the membarrier kselftest and Userspace RCU regression tests (the latter manually wired up on sys_membarrier) work fine. Tested-by: Mathieu Desnoyers <mathieu.desnoyers-vg+e7yoeK/dWk0Htik3J/w@public.gmane.org> sys_membarrier has been pulled into Linux 4.3-rc1. Please feel free to wire it up on ARM.Well, it's not going to end up with 388, but 389, because we also have userfaultfd added in the same merge window, and I follow the x86 syscall ordering when adding to ARM.
That's fine with me! Thanks, Mathieu
-- FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up according to speedtest.net.
-- Mathieu Desnoyers EfficiOS Inc. http://www.efficios.com