Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1214313
| From | Mathieu Desnoyers <mathieu.desnoyers@efficios.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Allocating sys_membarrier syscall number on other archs |
| Date | 2015-08-27 06:20 +0200 |
| Message-ID | <q1WPo-1MV-11@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
Allocating sys_membarrier syscall number on other archs Mathieu Desnoyers <mathieu.desnoyers@efficios.com> - 2015-08-27 06:20 +0200 Re: Allocating sys_membarrier syscall number on other archs Andrew Morton <akpm@linux-foundation.org> - 2015-08-27 06:20 +0200
csiph-web