Re: [PATCH 0/3] sys_membarrier (x86, generic)

2015-10-08 Thread Rusty Russell
Mathieu Desnoyers writes: > - On Oct 5, 2015, at 7:21 PM, Rusty Russell ru...@ozlabs.org wrote: > >> Mathieu Desnoyers writes: >>> Hi Andrew, >>> >>> Here is a repost of sys_membarrier, rebased on top of Linus commit >>> c4b5fd3fb2058b650447372472ad24e2a989f9f6 without any change since the >>

Re: [PATCH 0/3] sys_membarrier (x86, generic)

2015-10-05 Thread Mathieu Desnoyers
- On Oct 5, 2015, at 7:21 PM, Rusty Russell ru...@ozlabs.org wrote: > Mathieu Desnoyers writes: >> Hi Andrew, >> >> Here is a repost of sys_membarrier, rebased on top of Linus commit >> c4b5fd3fb2058b650447372472ad24e2a989f9f6 without any change since the >> last v19 post other that proceedin

Re: [PATCH 0/3] sys_membarrier (x86, generic)

2015-10-05 Thread Rusty Russell
Mathieu Desnoyers writes: > Hi Andrew, > > Here is a repost of sys_membarrier, rebased on top of Linus commit > c4b5fd3fb2058b650447372472ad24e2a989f9f6 without any change since the > last v19 post other that proceeding to further testing. When merging > with other system calls, system call number

[PATCH 0/3] sys_membarrier (x86, generic)

2015-07-10 Thread Mathieu Desnoyers
Hi Andrew, Here is a repost of sys_membarrier, rebased on top of Linus commit c4b5fd3fb2058b650447372472ad24e2a989f9f6 without any change since the last v19 post other that proceeding to further testing. When merging with other system calls, system call number conflicts should be quite straightfor