From: DanPartelly <DanPartelly@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Linux Kernel CONFIG_DEBUG_INFO_BTF by default
Date: Wed, 22 Jul 2020 13:16:27 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23723@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]
New issue by DanPartelly on void-packages repository
https://github.com/void-linux/void-packages/issues/23723
Description:
Please consider changing the default kernel config to include BTF deduplicated type information. The flag is CONFIG_DEBUG_INFO_BTF . The flag allow the kernel to make available type information to BPF programs, allowing those to introspect kernel structures without resorting to llvm/clang to parse kernel headers as was done in past by iovisor bcc tool for example. This was iffy at times and broke many times. BTF allows a lot of introspection into running kernel, making the setting usefull to all kind of ppl from developer to ops and sytem admins. given this usefulness more and more distros are enabling it by default. It is a relative recent addition, so the config flag should only be upaded for latest kernel serie (5.7) and up.
Note that when using this config, pahole utility becomes a build dependency.
BTF type info is de-duplicated and greatly reduced in size compared to dwarf. A primer into its usefulness can be read at:
https://facebookmicrosites.github.io/bpf/blog/2018/11/14/btf-enhancement.html
next reply other threads:[~2020-07-22 11:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 11:16 DanPartelly [this message]
2020-07-22 11:22 ` luhann
2020-08-12 11:47 ` leahneukirchen
2020-08-12 11:47 ` [ISSUE] [CLOSED] " leahneukirchen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23723@inbox.vuxu.org \
--to=danpartelly@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).