diff options
Diffstat (limited to 'Documentation/process/adding-syscalls.rst')
| -rw-r--r-- | Documentation/process/adding-syscalls.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/process/adding-syscalls.rst b/Documentation/process/adding-syscalls.rst index 314c8bf6f2a2..0d4f29bc798b 100644 --- a/Documentation/process/adding-syscalls.rst +++ b/Documentation/process/adding-syscalls.rst | |||
| @@ -360,7 +360,7 @@ First, the entry in ``arch/x86/entry/syscalls/syscall_32.tbl`` gets an extra | |||
| 360 | column to indicate that a 32-bit userspace program running on a 64-bit kernel | 360 | column to indicate that a 32-bit userspace program running on a 64-bit kernel |
| 361 | should hit the compat entry point:: | 361 | should hit the compat entry point:: |
| 362 | 362 | ||
| 363 | 380 i386 xyzzy sys_xyzzy compat_sys_xyzzy | 363 | 380 i386 xyzzy sys_xyzzy __ia32_compat_sys_xyzzy |
| 364 | 364 | ||
| 365 | Second, you need to figure out what should happen for the x32 ABI version of | 365 | Second, you need to figure out what should happen for the x32 ABI version of |
| 366 | the new system call. There's a choice here: the layout of the arguments | 366 | the new system call. There's a choice here: the layout of the arguments |
| @@ -373,7 +373,7 @@ the compatibility wrapper:: | |||
| 373 | 373 | ||
| 374 | 333 64 xyzzy sys_xyzzy | 374 | 333 64 xyzzy sys_xyzzy |
| 375 | ... | 375 | ... |
| 376 | 555 x32 xyzzy compat_sys_xyzzy | 376 | 555 x32 xyzzy __x32_compat_sys_xyzzy |
| 377 | 377 | ||
| 378 | If no pointers are involved, then it is preferable to re-use the 64-bit system | 378 | If no pointers are involved, then it is preferable to re-use the 64-bit system |
| 379 | call for the x32 ABI (and consequently the entry in | 379 | call for the x32 ABI (and consequently the entry in |
