Re: [RFC PATCH v2 6/9] arm: allocate sys_membarrier system call number

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Sep 16, 2015 at 06:27:10PM +0000, Mathieu Desnoyers wrote:
> ----- On Sep 7, 2015, at 12:15 PM, Mathieu Desnoyers mathieu.desnoyers@xxxxxxxxxxxx wrote:
> 
> > [ 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@xxxxxxxxxxxx>
> 
> 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.

-- 
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
--
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



[Index of Archives]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux