Page MenuHomeFreeBSD

syscall(2): make i386 less of an outlier
ClosedPublic

Authored by brooks on Mar 5 2024, 9:49 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Apr 7, 4:13 AM
Unknown Object (File)
Mar 7 2026, 10:06 AM
Unknown Object (File)
Mar 2 2026, 4:49 AM
Unknown Object (File)
Feb 28 2026, 3:04 AM
Unknown Object (File)
Feb 26 2026, 8:24 AM
Unknown Object (File)
Feb 25 2026, 2:15 PM
Unknown Object (File)
Feb 22 2026, 2:09 PM
Unknown Object (File)
Feb 15 2026, 7:31 AM
Subscribers

Details

Summary

Unlike other architectures, i386 only defined syscall() and not
_syscall() or sys_syscall(). The syscall() function then invoked the
desired system call directly rather than invoking syscall(2). Keep the
latter as it's marginally more efficent, but also create the
conventional _syscall() and
sys_syscall() stubs.

This avoids the need to special case syscall(2) in the symbol list
generation in libsys.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable