Github messages for voidlinux
 help / color / mirror / Atom feed
From: egorenar <egorenar@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] linux5.7: enable BPF type format on x86_64
Date: Sat, 25 Jul 2020 10:18:21 +0200	[thread overview]
Message-ID: <20200725081821.bOlqaDYI1DxgW7ltik8x7NuosHWiZ2d8VH-Wo-yom9I@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23534@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 548 bytes --]

There is an updated pull request by egorenar against master on the void-packages repository

https://github.com/egorenar/void-packages linux-5.7-enable-btf-x86_64
https://github.com/void-linux/void-packages/pull/23534

linux5.7: enable BPF type format on x86_64
Required e.g. for opensnoop from bcc-tools to fix the following problem:
libbpf: failed to find valid kernel BTF
libbpf: vmlinux BTF is not found
bpf: Failed to load program: Invalid argument

A patch file from https://github.com/void-linux/void-packages/pull/23534.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-linux-5.7-enable-btf-x86_64-23534.patch --]
[-- Type: text/x-diff, Size: 1558 bytes --]

From 370aaf60363dca37308dda58f91697ddee604597 Mon Sep 17 00:00:00 2001
From: Alexander Egorenkov <egorenar-dev@posteo.net>
Date: Sun, 12 Jul 2020 11:59:15 +0200
Subject: [PATCH] linux5.7: enable BPF type format on x86_64

Required e.g. for opensnoop from bcc-tools to fix the following problem:
libbpf: failed to find valid kernel BTF
libbpf: vmlinux BTF is not found
bpf: Failed to load program: Invalid argument
---
 srcpkgs/linux5.7/files/x86_64-dotconfig | 2 +-
 srcpkgs/linux5.7/template               | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/linux5.7/files/x86_64-dotconfig b/srcpkgs/linux5.7/files/x86_64-dotconfig
index 051a8db9923..9a94b7d6a16 100644
--- a/srcpkgs/linux5.7/files/x86_64-dotconfig
+++ b/srcpkgs/linux5.7/files/x86_64-dotconfig
@@ -9563,7 +9563,7 @@ CONFIG_DEBUG_INFO=y
 # CONFIG_DEBUG_INFO_REDUCED is not set
 # CONFIG_DEBUG_INFO_SPLIT is not set
 # CONFIG_DEBUG_INFO_DWARF4 is not set
-# CONFIG_DEBUG_INFO_BTF is not set
+CONFIG_DEBUG_INFO_BTF=y
 # CONFIG_GDB_SCRIPTS is not set
 # CONFIG_ENABLE_MUST_CHECK is not set
 CONFIG_FRAME_WARN=1024
diff --git a/srcpkgs/linux5.7/template b/srcpkgs/linux5.7/template
index 7a250fb34c5..3b435f9b5c8 100644
--- a/srcpkgs/linux5.7/template
+++ b/srcpkgs/linux5.7/template
@@ -22,7 +22,7 @@ noshlibprovides=yes
 preserve=yes
 
 hostmakedepends="tar xz bc elfutils-devel flex gmp-devel kmod libmpc-devel
- libressl-devel perl uboot-mkimage cpio"
+ libressl-devel perl uboot-mkimage cpio pahole"
 
 _kernver="${version}_${revision}"
 triggers="kernel-hooks"

  parent reply	other threads:[~2020-07-25  8:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-12 10:02 [PR PATCH] " egorenar
2020-07-23 13:39 ` ahesford
2020-07-23 13:39 ` ahesford
2020-07-24 18:37 ` [PR PATCH] [Updated] " egorenar
2020-07-25  8:18 ` egorenar [this message]
2020-08-04 13:26 ` leahneukirchen
2020-08-04 15:06 ` q66
2020-08-04 15:18 ` leahneukirchen
2020-08-04 15:18 ` [PR PATCH] [Merged]: " 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=20200725081821.bOlqaDYI1DxgW7ltik8x7NuosHWiZ2d8VH-Wo-yom9I@z \
    --to=egorenar@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).