From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752510AbbH0EPQ (ORCPT ); Thu, 27 Aug 2015 00:15:16 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:40992 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751834AbbH0EPO (ORCPT ); Thu, 27 Aug 2015 00:15:14 -0400 Date: Wed, 26 Aug 2015 21:15:24 -0700 From: Andrew Morton To: Mathieu Desnoyers Cc: LKML , linux-api Subject: Re: Allocating sys_membarrier syscall number on other archs Message-Id: <20150826211524.c45393c7.akpm@linux-foundation.org> In-Reply-To: <1721242013.30076.1440648282669.JavaMail.zimbra@efficios.com> References: <1721242013.30076.1440648282669.JavaMail.zimbra@efficios.com> X-Mailer: Sylpheed 2.7.1 (GTK+ 2.18.9; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 27 Aug 2015 04:04:42 +0000 (UTC) Mathieu Desnoyers 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 ;)