Lines Matching +full:64 +full:bit

151 offset within a file, make its type ``loff_t`` so that 64-bit offsets can be
152 supported even on 32-bit architectures.
155 it needs to be governed by the appropriate Linux capability bit (checked with
157 page.  Choose an existing capability bit that governs related functionality,
159 under the same bit, as this goes against capabilities' purpose of splitting
170 system call parameters that are explicitly 64-bit fall on odd-numbered
171 arguments (i.e. parameter 1, 3, 5), to allow use of contiguous pairs of 32-bit
272 For most system calls the same 64-bit implementation can be invoked even when
273 the userspace program is itself 32-bit; even if the system call's parameters
277 needed to cope with size differences between 32-bit and 64-bit.
279 The first is if the 64-bit kernel also supports 32-bit userspace programs, and
280 so needs to parse areas of (``__user``) memory that could hold either 32-bit or
281 64-bit values.  In particular, this is needed whenever a system call argument
291 system call's arguments has a type that is explicitly 64-bit even on a 32-bit
293 arrives at a 64-bit kernel from a 32-bit application will be split into two
294 32-bit values, which then need to be re-assembled in the compatibility layer.
296 (Note that a system call argument that's a pointer to an explicit 64-bit type
302 SYSCALL_DEFINEn.  This version of the implementation runs as part of a 64-bit
303 kernel, but expects to receive 32-bit parameter values and does whatever is
305 values to 64-bit versions and either calls on to the ``sys_`` version, or both of
314 If the system call involves a structure that is laid out differently on 32-bit
315 and 64-bit systems, say ``struct xyzzy_args``, then the include/linux/compat.h
320 parse the arguments from a 32-bit invocation.
351  - (if needed) 32-bit mapping struct in ``include/linux/compat.h``
363 column to indicate that a 32-bit userspace program running on a 64-bit kernel
370 should either match the 64-bit version or the 32-bit version.
373 ILP32, so the layout should match the 32-bit version, and the entry in
377     333   64       xyzzy     sys_xyzzy
381 If no pointers are involved, then it is preferable to re-use the 64-bit system
386 layout do indeed map exactly from x32 (-mx32) to either the 32-bit (-m32) or
387 64-bit (-m64) equivalents.
417 The equivalent for 32-bit programs running on a 64-bit kernel is normally
426 of the system call rather than the native 64-bit version.  Also, if the x32 ABI
508 At least on 64-bit x86, it will be a hard requirement from v4.17 onwards to not
532  - LWN article from Jake Edge describing constraints on 64-bit system call
571  - Discussion from Matthew Wilcox about restrictions on 64-bit arguments:
576    compatibility with 64-bit versions rather than 32-bit versions: