From: Anh Tuan Phan <tuananhlfc@gmail.com>
To: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: [PATCH v2] samples/bpf: Add more instructions to build dependencies and, configuration in README.rst
Date: Thu, 6 Jul 2023 23:00:06 +0700 [thread overview]
Message-ID: <bd1477f2-a51e-a795-4f25-a32d6ab46530@gmail.com> (raw)
Update the Documentation to mention that some samples require pahole
v1.16 and kernel built with CONFIG_DEBUG_INFO_BTF=y
Signed-off-by: Anh Tuan Phan <tuananhlfc@gmail.com>
---
samples/bpf/README.rst | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/samples/bpf/README.rst b/samples/bpf/README.rst
index 57f93edd1957..631592b83d60 100644
--- a/samples/bpf/README.rst
+++ b/samples/bpf/README.rst
@@ -14,6 +14,9 @@ Compiling requires having installed:
Note that LLVM's tool 'llc' must support target 'bpf', list version
and supported targets with command: ``llc --version``
+Some samples require pahole version 1.16 as a dependency. See
+https://docs.kernel.org/bpf/bpf_devel_QA.html for reference.
+
Clean and configuration
-----------------------
@@ -28,6 +31,10 @@ Configure kernel, defconfig for instance::
make defconfig
+Some samples require support for BPF Type Format (BTF). To enable it,
open the
+generated config file, or use menuconfig (by "make menuconfig") to
enable the
+following configs: CONFIG_BPF_SYSCALL and CONFIG_DEBUG_INFO_BTF.
+
Kernel headers
--------------
--
2.34.1
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
next reply other threads:[~2023-07-06 16:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 16:00 Anh Tuan Phan [this message]
2023-07-06 18:16 ` [PATCH v2] samples/bpf: Add more instructions to build dependencies and, configuration in README.rst Stanislav Fomichev via Linux-kernel-mentees
2023-07-07 13:48 ` Anh Tuan Phan
2023-07-07 16:57 ` Stanislav Fomichev via Linux-kernel-mentees
2023-07-09 14:37 ` Anh Tuan Phan
2023-07-09 15:21 ` Khalid Masum
2023-07-09 15:36 ` Siddh Raman Pant
2023-07-10 13:03 ` Anh Tuan Phan
2023-07-11 12:53 ` Siddh Raman Pant
2023-07-10 12:58 ` Anh Tuan Phan
2023-07-10 17:21 ` Stanislav Fomichev via Linux-kernel-mentees
2023-07-06 19:43 ` Ivan Orlov
2023-07-07 13:51 ` Anh Tuan Phan
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=bd1477f2-a51e-a795-4f25-a32d6ab46530@gmail.com \
--to=tuananhlfc@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=martin.lau@linux.dev \
/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