From: Daniel Borkmann <daniel@iogearbox.net>
To: Andrii Nakryiko <andriin@fb.com>,
bpf@vger.kernel.org, netdev@vger.kernel.org, ast@fb.com,
acme@redhat.com
Cc: andrii.nakryiko@gmail.com, kernel-team@fb.com
Subject: Re: [PATCH bpf-next 0/2] libbpf: make use of BTF through sysfs
Date: Tue, 13 Aug 2019 23:22:40 +0200 [thread overview]
Message-ID: <176f6ecc-dcd3-e646-f812-a2cb2a2b446b@iogearbox.net> (raw)
In-Reply-To: <20190813185443.437829-1-andriin@fb.com>
On 8/13/19 8:54 PM, Andrii Nakryiko wrote:
> Now that kernel's BTF is exposed through sysfs at well-known location, attempt
> to load it first as a target BTF for the purpose of BPF CO-RE relocations.
>
> Patch #1 is a follow-up patch to rename /sys/kernel/btf/kernel into
> /sys/kernel/btf/vmlinux.
> Patch #2 adds ability to load raw BTF contents from sysfs and expands the list
> of locations libbpf attempts to load vmlinux BTF from.
>
> Andrii Nakryiko (2):
> btf: rename /sys/kernel/btf/kernel into /sys/kernel/btf/vmlinux
> libbpf: attempt to load kernel BTF from sysfs first
>
> Documentation/ABI/testing/sysfs-kernel-btf | 2 +-
> kernel/bpf/sysfs_btf.c | 30 +++++-----
> scripts/link-vmlinux.sh | 18 +++---
> tools/lib/bpf/libbpf.c | 64 +++++++++++++++++++---
> 4 files changed, 82 insertions(+), 32 deletions(-)
>
LGTM, applied thanks!
prev parent reply other threads:[~2019-08-13 21:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 18:54 [PATCH bpf-next 0/2] libbpf: make use of BTF through sysfs Andrii Nakryiko
2019-08-13 18:54 ` [PATCH bpf-next 1/2] btf: rename /sys/kernel/btf/kernel into /sys/kernel/btf/vmlinux Andrii Nakryiko
2019-08-13 18:54 ` [PATCH bpf-next 2/2] libbpf: attempt to load kernel BTF from sysfs first Andrii Nakryiko
2019-08-13 21:22 ` Daniel Borkmann [this message]
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=176f6ecc-dcd3-e646-f812-a2cb2a2b446b@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=acme@redhat.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andriin@fb.com \
--cc=ast@fb.com \
--cc=bpf@vger.kernel.org \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.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).