bpf: Update bpf_design_QA.rst to clarify that BTF_ID does not ABIify a function
This patch updates bpf_design_QA.rst to clarify that mentioning a function to the BTF_ID macro does not make that function become part of the Linux kernel's ABI. Suggested-by: Alexei Starovoitov <alexei.starovoitov@gmail.com> Signed-off-by: Paul E. McKenney <paulmck@kernel.org> Link: https://lore.kernel.org/r/20220802173913.4170192-3-paulmck@kernel.org Signed-off-by: Alexei Starovoitov <ast@kernel.org>
This commit is contained in:
parent
62fc770d90
commit
8fcf19696a
|
@ -291,3 +291,10 @@ The kernel function prototypes will change, and BPF programs attaching to
|
||||||
them will need to change. The BPF compile-once-run-everywhere (CO-RE)
|
them will need to change. The BPF compile-once-run-everywhere (CO-RE)
|
||||||
should be used in order to make it easier to adapt your BPF programs to
|
should be used in order to make it easier to adapt your BPF programs to
|
||||||
different versions of the kernel.
|
different versions of the kernel.
|
||||||
|
|
||||||
|
Q: Marking a function with BTF_ID makes that function an ABI?
|
||||||
|
-------------------------------------------------------------
|
||||||
|
A: NO.
|
||||||
|
|
||||||
|
The BTF_ID macro does not cause a function to become part of the ABI
|
||||||
|
any more than does the EXPORT_SYMBOL_GPL macro.
|
||||||
|
|
Loading…
Reference in New Issue