linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon@arm.com>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Catalin Marinas <Catalin.Marinas@arm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-api <linux-api@vger.kernel.org>
Subject: Re: [RFC PATCH v2 7/9] arm64: allocate sys_membarrier system call number
Date: Wed, 16 Sep 2015 17:35:27 +0100	[thread overview]
Message-ID: <20150916163527.GO28771@arm.com> (raw)
In-Reply-To: <4692929.9334.1442416719904.JavaMail.zimbra@efficios.com>

Hi Mathieu,

On Wed, Sep 16, 2015 at 04:18:39PM +0100, Mathieu Desnoyers wrote:
> ----- On Sep 7, 2015, at 12:15 PM, Mathieu Desnoyers mathieu.desnoyers@efficios.com wrote:
> 
> > arm64 sys_membarrier number is already wired for arm64 through
> > asm-generic/unistd.h, but needs to be allocated separately for
> > the 32-bit compability layer of arm64.
> > 
> > [ Untested on this architecture. To try it out: fetch linux-next/akpm,
> >  apply this patch, build/run a membarrier-enabled kernel, and do make
> >  kselftest. ]
> 
> sys_membarrier has been merged into Linux 4.3-rc1. sys_membarrier can therefore
> be tested on top of Linus' master.

Just to say that I'm happy to merge this once arch/arm/ also has the
syscall wired up. It'd be a bit weird to have the support in the arm64
compat layer but not the arch/arm/ native kernel!

Will

  reply	other threads:[~2015-09-16 16:35 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-07 16:15 [PATCH v2 0/9] Allocate sys_membarrier on main architectures Mathieu Desnoyers
2015-09-07 16:15 ` [PATCH v2 1/9] [picked] powerpc: allocate sys_membarrier system call number Mathieu Desnoyers
2015-09-07 16:15 ` [PATCH v2 2/9] mips: " Mathieu Desnoyers
2015-09-16 15:04   ` Mathieu Desnoyers
2015-09-28 17:12     ` Mathieu Desnoyers
2015-09-07 16:15 ` [PATCH v2 3/9] sparc/sparc64: " Mathieu Desnoyers
2015-09-16 15:05   ` Mathieu Desnoyers
2015-09-16 17:57     ` David Miller
2015-09-16 18:06       ` Mathieu Desnoyers
2015-09-07 16:15 ` [PATCH v2 4/9] parisc: " Mathieu Desnoyers
2015-09-16 15:07   ` Mathieu Desnoyers
2015-09-16 19:56     ` Helge Deller
2015-09-07 16:15 ` [RFC PATCH v2 5/9] alpha: " Mathieu Desnoyers
2015-09-16 15:17   ` Mathieu Desnoyers
2015-09-07 16:15 ` [RFC PATCH v2 6/9] arm: " Mathieu Desnoyers
2015-09-16 18:27   ` Mathieu Desnoyers
2015-09-17 13:13     ` Russell King - ARM Linux
2015-09-17 13:37       ` Mathieu Desnoyers
2015-09-17 13:49         ` Russell King - ARM Linux
2015-09-07 16:15 ` [RFC PATCH v2 7/9] arm64: " Mathieu Desnoyers
2015-09-16 15:18   ` Mathieu Desnoyers
2015-09-16 16:35     ` Will Deacon [this message]
2015-09-16 16:38       ` Mathieu Desnoyers
2015-09-16 16:39         ` Will Deacon
2015-09-07 16:15 ` [RFC PATCH v2 8/9] ia64: " Mathieu Desnoyers
2015-09-16 15:19   ` Mathieu Desnoyers
2015-09-07 16:15 ` [RFC PATCH v2 9/9] s390/s390x: " Mathieu Desnoyers
2015-09-16 15:20   ` Mathieu Desnoyers
2015-09-17 11:39     ` Martin Schwidefsky

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=20150916163527.GO28771@arm.com \
    --to=will.deacon@arm.com \
    --cc=Catalin.Marinas@arm.com \
    --cc=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;
as well as URLs for NNTP newsgroup(s).