Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1391272 > unrolled thread
| Started by | Catalin Marinas <catalin.marinas@arm.com> |
|---|---|
| First post | 2016-04-29 18:10 +0200 |
| Last post | 2016-04-29 18:20 +0200 |
| Articles | 2 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH 25/25] arm64:ilp32: add ARM64_ILP32 to Kconfig Catalin Marinas <catalin.marinas@arm.com> - 2016-04-29 18:10 +0200
Re: [PATCH 25/25] arm64:ilp32: add ARM64_ILP32 to Kconfig Catalin Marinas <catalin.marinas@arm.com> - 2016-04-29 18:20 +0200
| From | Catalin Marinas <catalin.marinas@arm.com> |
|---|---|
| Date | 2016-04-29 18:10 +0200 |
| Subject | Re: [PATCH 25/25] arm64:ilp32: add ARM64_ILP32 to Kconfig |
| Message-ID | <rtj9o-xI-9@gated-at.bofh.it> |
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
[toc] | [next] | [standalone]
| From | Catalin Marinas <catalin.marinas@arm.com> |
|---|---|
| Date | 2016-04-29 18:20 +0200 |
| Message-ID | <rtjj4-Bp-3@gated-at.bofh.it> |
| In reply to | #1391272 |
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
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web