[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160429160855.GA16451@yury-N73SV>
Date: Fri, 29 Apr 2016 19:08:55 +0300
From: Yury Norov <ynorov@...iumnetworks.com>
To: Catalin Marinas <catalin.marinas@....com>
CC: <arnd@...db.de>, <linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>, <linux-arch@...r.kernel.org>,
<linux-s390@...r.kernel.org>, <pinskia@...il.com>,
<Prasun.Kapoor@...iumnetworks.com>, <schwab@...e.de>,
<broonie@...nel.org>, <linux-doc@...r.kernel.org>,
<heiko.carstens@...ibm.com>, <agraf@...e.de>,
<klimov.linux@...il.com>,
Andrew Pinski <Andrew.Pinski@...iumnetworks.com>,
<bamvor.zhangjian@...wei.com>, Andrew Pinski <apinski@...ium.com>,
<schwidefsky@...ibm.com>, <Nathan_Lynch@...tor.com>,
Philipp Tomsich <philipp.tomsich@...obroma-systems.com>,
<joseph@...esourcery.com>,
<christoph.muellner@...obroma-systems.com>
Subject: Re: [PATCH 25/25] arm64:ilp32: add ARM64_ILP32 to Kconfig
On Fri, Apr 29, 2016 at 05:03:34PM +0100, Catalin Marinas wrote:
> On Wed, Apr 06, 2016 at 01:08:47AM +0300, Yury Norov wrote:
> > +config ARM64_ILP32
> > + bool "Kernel support for ILP32"
> > + select COMPAT_WRAPPER
> > + help
> > + This option enables support for AArch64 ILP32 user space. ILP32
> > + is an ABI where long and pointers are 32bits but it uses the AARCH64
> > + instruction set.
>
> Is there any penalty for AArch32 tasks when selecting COMPAT_WRAPPER?
>
> --
> Catalin
No. AARCH32 doesn't define __SC_WRAP and so __SYSCALL macro is used,
which fills syscall table with sys_xxx versions, not compat_sys_xxx.
Powered by blists - more mailing lists