From: Song Liu <song@kernel.org>
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf <bpf@vger.kernel.org>, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Kernel Team <kernel-team@fb.com>
Subject: Re: [PATCH bpf-next 2/3] libbpf: support target-less SEC() definitions for BTF-backed programs
Date: Fri, 8 Apr 2022 14:08:50 -0700 [thread overview]
Message-ID: <CAPhsuW6ZYEzibrw380sWVdHvOtJ7UtC=E_fT2ohYK_QUa-Zjqg@mail.gmail.com> (raw)
In-Reply-To: <20220408203433.2988727-3-andrii@kernel.org>
On Fri, Apr 8, 2022 at 1:34 PM Andrii Nakryiko <andrii@kernel.org> wrote:
>
> Similar to previous patch, support target-less definitions like
> SEC("fentry"), SEC("freplace"), etc. For such BTF-backed program types
> it is expected that user will specify BTF target programmatically at
> runtime using bpf_program__set_attach_target() *before* load phase. If
> not, libbpf will report this as an error.
>
> Aslo use SEC_ATTACH_BTF flag instead of explicitly listing a set of
> types that are expected to require attach_btf_id. This was an accidental
> omission during custom SEC() support refactoring.
>
> Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
Acked-by: Song Liu <songliubraving@fb.com>
next prev parent reply other threads:[~2022-04-08 21:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 20:34 [PATCH bpf-next 0/3] Add target-less tracing SEC() definitions Andrii Nakryiko
2022-04-08 20:34 ` [PATCH bpf-next 1/3] libbpf: allow "incomplete" basic " Andrii Nakryiko
2022-04-08 20:46 ` Song Liu
2022-04-08 22:21 ` Andrii Nakryiko
2022-04-08 22:36 ` Song Liu
2022-04-08 20:34 ` [PATCH bpf-next 2/3] libbpf: support target-less SEC() definitions for BTF-backed programs Andrii Nakryiko
2022-04-08 21:08 ` Song Liu [this message]
2022-04-08 20:34 ` [PATCH bpf-next 3/3] selftests/bpf: use target-less SEC() definitions in various tests Andrii Nakryiko
2022-04-08 21:08 ` Song Liu
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='CAPhsuW6ZYEzibrw380sWVdHvOtJ7UtC=E_fT2ohYK_QUa-Zjqg@mail.gmail.com' \
--to=song@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.