Greg Kroah-Hartman
598cf27219
Link: https://lore.kernel.org/r/20260217200002.683975158@linuxfoundation.org Tested-by: Florian Fainelli <florian.fainelli@broadcom.com> Tested-by: Takeshi Ogasawara <takeshi.ogasawara@futuring-girl.com> Tested-by: Peter Schneider <pschneider1968@googlemail.com> Tested-by: Jon Hunter <jonathanh@nvidia.com> Tested-by: Salvatore Bonaccorso <carnil@debian.org> Tested-by: Brett A C Sheffield <bacs@librecast.net> Tested-by: Mark Brown <broonie@kernel.org> Tested-by: Luna Jernberg <droidbittin@gmail.com> Tested-by: Ronald Warsow <rwarsow@gmx.de> Tested-by: Justin M. Forbes <jforbes@fedoraproject.org> Tested-by: Ron Economos <re@w6rz.net> Tested-by: Miguel Ojeda <ojeda@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
29 lines
968 B
ReStructuredText
29 lines
968 B
ReStructuredText
.. contents::
|
|
.. sectnum::
|
|
|
|
===================================================
|
|
BPF ABI Recommended Conventions and Guidelines v1.0
|
|
===================================================
|
|
|
|
This is version 1.0 of an informational document containing recommended
|
|
conventions and guidelines for producing portable BPF program binaries.
|
|
|
|
Registers and calling convention
|
|
================================
|
|
|
|
BPF has 10 general purpose registers and a read-only frame pointer register,
|
|
all of which are 64-bits wide.
|
|
|
|
The BPF calling convention is defined as:
|
|
|
|
* R0: return value from function calls, and exit value for BPF programs
|
|
* R1 - R5: arguments for function calls
|
|
* R6 - R9: callee saved registers that function calls will preserve
|
|
* R10: read-only frame pointer to access stack
|
|
|
|
R0 - R5 are scratch registers and BPF programs needs to spill/fill them if
|
|
necessary across calls.
|
|
|
|
The BPF program needs to store the return value into register R0 before doing an
|
|
``EXIT``.
|