From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-api <linux-api@vger.kernel.org>,
Michael Jeanson <mjeanson@efficios.com>
Subject: Re: [RFC PATCH v2 6/9] arm: allocate sys_membarrier system call number
Date: Thu, 17 Sep 2015 14:13:16 +0100 [thread overview]
Message-ID: <20150917131316.GO21084@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <2106738851.9514.1442428030540.JavaMail.zimbra@efficios.com>
On Wed, Sep 16, 2015 at 06:27:10PM +0000, Mathieu Desnoyers wrote:
> ----- On Sep 7, 2015, at 12:15 PM, Mathieu Desnoyers mathieu.desnoyers@efficios.com wrote:
>
> > [ 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. ]
>
> Hi,
>
> We tested the system call on our ARM board (Wandboard, SoC
> Freescale i.MX6 Quad) by applying this patch on top of
> Linux 4.3-rc1. Both the membarrier kselftest and
> Userspace RCU regression tests (the latter manually wired up
> on sys_membarrier) work fine.
>
> Tested-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
>
> sys_membarrier has been pulled into Linux 4.3-rc1. Please
> feel free to wire it up on ARM.
Well, it's not going to end up with 388, but 389, because we also have
userfaultfd added in the same merge window, and I follow the x86
syscall ordering when adding to ARM.
--
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2015-09-17 13:13 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 [this message]
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
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=20150917131316.GO21084@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mjeanson@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
all inboxes | Powered by JetHome®