Allocating sys_membarrier syscall number on other archs

Allocating sys_membarrier syscall number on other archs

[Mathieu Desnoyers]

Hi Andrew,

The sys_membarrier patches you have in your tree target
x86 32-64 and generic, but I did not allocate the system call
number on other architectures to minimize the amount of
collisions, and because I do not have all those architectures
handy.

How would you recommend to proceed to allocate those ?

sys_membarrier is pretty much architecture agnostic: it
takes two integer parameters, and the only function it calls,
synchronize_sched(), is available on all architectures.

Thanks,

Mathieu

-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com

Re: Allocating sys_membarrier syscall number on other archs

[Andrew Morton]

On Thu, 27 Aug 2015 04:04:42 +0000 (UTC) Mathieu Desnoyers <mathieu.desnoyers@efficios.com> wrote:

> Hi Andrew,
> 
> The sys_membarrier patches you have in your tree target
> x86 32-64 and generic, but I did not allocate the system call
> number on other architectures to minimize the amount of
> collisions, and because I do not have all those architectures
> handy.
> 
> How would you recommend to proceed to allocate those ?
> 

I don't think you need to do anything.  You've provided the selftest
code for the arch maintainers and the arch maintainers will get
"membarrier not implemented" warnings each time they build a kernel. 
The idea is that when they have time they'll wire it up, run the tests
then ship it.

If you want to help that process along a bit you could send patches to
the arch maintainers along with instructions on how to test the
syscall.  The less work they have to do, the more likely they are
to do it ;)