[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2075941251.9404.1442421484155.JavaMail.zimbra@efficios.com>
Date: Wed, 16 Sep 2015 16:38:04 +0000 (UTC)
From: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
To: Will Deacon <will.deacon@....com>
Cc: Catalin Marinas <Catalin.Marinas@....com>,
linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
linux-api <linux-api@...r.kernel.org>
Subject: Re: [RFC PATCH v2 7/9] arm64: allocate sys_membarrier system call
number
----- On Sep 16, 2015, at 12:35 PM, Will Deacon will.deacon@....com wrote:
> 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@...icios.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!
Sounds good! We're currently testing sys_membarrier on a wandboard. We'll
provide feedback by replying to the ARM patch thread soon.
Thanks,
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists