Lines Matching refs:x86

159 Finally, be aware that some non-x86 architectures have an easier time if
176    x86 (including all of x86_64, x86_32 and x32).
203 Some architectures (e.g. x86) have their own architecture-specific syscall
241 x86 System Call Implementation
244 To wire up your new system call for x86 platforms, you need to update the
247 arch/x86/entry/syscalls/syscall_64.tbl:
251 and an "i386" entry in arch/x86/entry/syscalls/syscall_32.tbl:
344 Compatibility System Calls (x86)
347 To wire up the x86 architecture of a system call with a compatibility version,
350 First, the entry in arch/x86/entry/syscalls/syscall_32.tbl gets an extra
362 arch/x86/entry/syscalls/syscall_64.tbl is split so that x32 programs hit the
371 arch/x86/entry/syscalls/syscall_64.tbl is unchanged).
399 arch/x86/entry/entry_64.S, and the entry in the syscall table
400 (arch/x86/entry/syscalls/syscall_64.tbl) is adjusted to match:
405 called stub32_xyzzy and implemented in arch/x86/entry/entry_64_compat.S,
407 arch/x86/entry/syscalls/syscall_32.tbl:
420 doesn't include arch/x86/entry/entry_64.S implementation (because UML
422 arch/x86/um/sys_call_table_64.c:
506  - Suggestion from Thomas Gleixner that x86 wire-up should be in a separate