From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-api <linux-api@vger.kernel.org>,
linux-kernel@vger.kernel.org,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [RFC PATCH 1/9] powerpc: allocate sys_membarrier system call number
Date: Mon, 31 Aug 2015 15:32:54 +0000 (UTC) [thread overview]
Message-ID: <131898944.32688.1441035174419.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <1441004045.5735.8.camel@ellerman.id.au>
----- On Aug 31, 2015, at 2:54 AM, Michael Ellerman mpe@ellerman.id.au wrote:
> On Thu, 2015-08-27 at 13:56 -0400, Mathieu Desnoyers wrote:
>> Allow it to be used from SPU, since it should not have unwanted
>> side-effects.
>>
>> [ 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. ]
>>
>> Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
>> CC: Andrew Morton <akpm@linux-foundation.org>
>> CC: linux-api@vger.kernel.org
>> CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
>> CC: Paul Mackerras <paulus@samba.org>
>> CC: Michael Ellerman <mpe@ellerman.id.au>
>> CC: linuxppc-dev@lists.ozlabs.org
>
> Thanks.
>
> I get:
>
> $ ./membarrier_test
> membarrier MEMBARRIER_CMD_QUERY syscall available.
> membarrier: MEMBARRIER_CMD_SHARED success.
> membarrier: tests done!
>
> Which looks good.
>
> Assuming the membarrier support hits 4.3, I'll take this via my tree for 4.3
> also.
Great! I'll take care of your comments about self-tests,
Thanks,
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2015-08-31 15:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 17:56 [RFC PATCH 0/9] allocate sys_membarrier system call number on major archs Mathieu Desnoyers
2015-08-27 17:56 ` [RFC PATCH 1/9] powerpc: allocate sys_membarrier system call number Mathieu Desnoyers
2015-08-31 6:54 ` Michael Ellerman
2015-08-31 15:32 ` Mathieu Desnoyers [this message]
2015-09-01 1:00 ` Michael Ellerman
2015-08-27 17:56 ` [RFC PATCH 2/9] arm: " Mathieu Desnoyers
2015-08-27 22:51 ` Russell King - ARM Linux
2015-08-27 23:16 ` Mathieu Desnoyers
2015-08-27 17:56 ` [RFC PATCH 3/9] arm64: " Mathieu Desnoyers
2015-09-02 10:10 ` Will Deacon
2015-09-03 15:38 ` Mathieu Desnoyers
2015-08-27 17:56 ` [RFC PATCH 4/9] mips: " Mathieu Desnoyers
2015-08-28 7:40 ` Ralf Baechle
2015-08-28 14:06 ` Mathieu Desnoyers
2015-08-27 17:56 ` [RFC PATCH 5/9] s390/s390x: " Mathieu Desnoyers
2015-08-27 17:56 ` [RFC PATCH 6/9] sparc/sparc64: " Mathieu Desnoyers
2015-08-27 23:16 ` David Miller
2015-08-27 17:56 ` [RFC PATCH 7/9] alpha: " Mathieu Desnoyers
2015-08-27 18:34 ` Matt Turner
2015-08-27 19:06 ` Mathieu Desnoyers
2015-08-27 19:07 ` [RFC PATCH v2] " Mathieu Desnoyers
2015-08-27 17:56 ` [RFC PATCH 8/9] ia64: " Mathieu Desnoyers
2015-08-27 17:56 ` [RFC PATCH 9/9] parisc: " Mathieu Desnoyers
2015-09-03 12:26 ` Helge Deller
2015-09-03 15:41 ` Mathieu Desnoyers
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=131898944.32688.1441035174419.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
/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).