public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-api <linux-api@vger.kernel.org>
Subject: Re: Allocating sys_membarrier syscall number on other archs
Date: Wed, 26 Aug 2015 21:15:24 -0700	[thread overview]
Message-ID: <20150826211524.c45393c7.akpm@linux-foundation.org> (raw)
In-Reply-To: <1721242013.30076.1440648282669.JavaMail.zimbra@efficios.com>

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 ;)



      reply	other threads:[~2015-08-27  4:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-27  4:04 Allocating sys_membarrier syscall number on other archs Mathieu Desnoyers
2015-08-27  4:15 ` Andrew Morton [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150826211524.c45393c7.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox