-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
armbian-kernel.sh: introduce KERNEL_BTF=no
to opt-out of BTF/CO-RE type-info on low-RAM machines
#7675
Conversation
4092bf5
to
ab6192d
Compare
ab6192d
to
cf72bb4
Compare
…type-info on low-RAM machines - turns out `pahole` for `vmlinux` can take multiple gigabytes of RAM to run successfully - I can't simply decide based on available RAM, as that would make .config hashes mismatch - thus, introduce: - default is to enable BTF; if on low-ram host, error out unless KERNEL_BTF=yes is passed - if KERNEL_BTF=no is passed, the BTF debug info is always disabled - if KERNEL_BTF=yes is passed, then a warning is produced, but BTF is still enabled - the magic number "6451 MiB" was determined empirically (and is probably bs)
cf72bb4
to
2a65b10
Compare
Merging to 25.02 ? Can something be added to the docs as this is new features. |
Docs would go along the lines of
|
When changing KERNEL_BTF it does not recompile kernel. Is this expected? armhf / mvebu |
Might be it was already disabled there? Still the hash change should cause at least some recompile. |
Yes, it was there. |
Then it is not working the way I intended it to. Can you post the |
armbian-kernel.sh: introduce
KERNEL_BTF=no
to opt-out of BTF/CO-RE type-info on low-RAM machinesKERNEL_BTF=no
to opt-out of BTF/CO-RE type-info on low-RAM machinespahole
forvmlinux
can take multiple gigabytes of RAM to run successfully