Message ID | 1459894127-17698-26-git-send-email-ynorov@caviumnetworks.com |
---|---|
State | Superseded |
Headers | show |
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
On Fri, Apr 29, 2016 at 07:08:55PM +0300, Yury Norov wrote: > 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? > > 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. Ah, I forgot it has its own unistd32.h. Thanks. -- Catalin
diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig index 46fc295..19d8e31 100644 --- a/arch/arm64/Kconfig +++ b/arch/arm64/Kconfig @@ -926,7 +926,7 @@ source "fs/Kconfig.binfmt" config COMPAT def_bool y - depends on AARCH32_EL0 + depends on AARCH32_EL0 || ARM64_ILP32 config AARCH32_EL0 bool "Kernel support for 32-bit EL0" @@ -946,6 +946,14 @@ config AARCH32_EL0 If you want to execute 32-bit userspace applications, say Y. +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. + config SYSVIPC_COMPAT def_bool y depends on COMPAT && SYSVIPC