From: Andrii Nakryiko <andrii.nakryiko@gmail.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>, bpf <bpf@vger.kernel.org>,
Kernel Team <kernel-team@fb.com>
Subject: Re: [PATCH v4 bpf-next 08/16] libbpf: Use CO-RE in the kernel in light skeleton.
Date: Mon, 29 Nov 2021 17:11:10 -0800 [thread overview]
Message-ID: <CAEf4Bza-NtGJMEtJ99T_y9FFykXHsVwwjqYZ_aFp6+M1Sqfsng@mail.gmail.com> (raw)
In-Reply-To: <20211124060209.493-9-alexei.starovoitov@gmail.com>
On Tue, Nov 23, 2021 at 10:02 PM Alexei Starovoitov
<alexei.starovoitov@gmail.com> wrote:
>
> From: Alexei Starovoitov <ast@kernel.org>
>
> Without lskel the CO-RE relocations are processed by libbpf before any other
> work is done. Instead, when lskel is needed, remember relocation as RELO_CORE
> kind. Then when loader prog is generated for a given bpf program pass CO-RE
> relos of that program to gen loader via bpf_gen__record_relo_core(). The gen
> loader will remember them as-is and pass it later as-is into the kernel.
>
> The normal libbpf flow is to process CO-RE early before call relos happen. In
> case of gen_loader the core relos have to be added to other relos to be copied
> together when bpf static function is appended in different places to other main
> bpf progs. During the copy the append_subprog_relos() will adjust insn_idx for
> normal relos and for RELO_CORE kind too. When that is done each struct
> reloc_desc has good relos for specific main prog.
>
> Signed-off-by: Alexei Starovoitov <ast@kernel.org>
> ---
> tools/lib/bpf/bpf_gen_internal.h | 3 +
> tools/lib/bpf/gen_loader.c | 41 +++++++++++-
> tools/lib/bpf/libbpf.c | 108 ++++++++++++++++++++++---------
> 3 files changed, 119 insertions(+), 33 deletions(-)
>
LGTM, minor styling nit, please address if/when resubmitting.
Acked-by: Andrii Nakryiko <andrii@kernel.org>
[...]
> @@ -6600,6 +6638,16 @@ static int bpf_program__record_externs(struct bpf_program *prog)
> ext->is_weak, false, BTF_KIND_FUNC,
> relo->insn_idx);
> break;
> + case RELO_CORE: {
> + struct bpf_core_relo cr = {
> + .insn_off = relo->insn_idx * 8,
> + .type_id = relo->core_relo->type_id,
> + .access_str_off = relo->core_relo->access_str_off,
> + .kind = relo->core_relo->kind,
> + };
nit: empty line between variable and statements
> + bpf_gen__record_relo_core(obj->gen_loader, &cr);
> + break;
> + }
> default:
> continue;
> }
> @@ -6639,7 +6687,7 @@ static int bpf_object_load_prog(struct bpf_object *obj, struct bpf_program *prog
> prog->name, prog->instances.nr);
> }
> if (obj->gen_loader)
> - bpf_program__record_externs(prog);
> + bpf_program_record_relos(prog);
> err = bpf_object_load_prog_instance(obj, prog,
> prog->insns, prog->insns_cnt,
> license, kern_ver, &fd);
> --
> 2.30.2
>
next prev parent reply other threads:[~2021-11-30 1:11 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 6:01 [PATCH v4 bpf-next 00/16] bpf: CO-RE support in the kernel Alexei Starovoitov
2021-11-24 6:01 ` [PATCH v4 bpf-next 01/16] libbpf: Replace btf__type_by_id() with btf_type_by_id() Alexei Starovoitov
2021-11-24 6:01 ` [PATCH v4 bpf-next 02/16] bpf: Rename btf_member accessors Alexei Starovoitov
2021-11-24 6:01 ` [PATCH v4 bpf-next 03/16] bpf: Prepare relo_core.c for kernel duty Alexei Starovoitov
2021-11-24 6:01 ` [PATCH v4 bpf-next 04/16] bpf: Define enum bpf_core_relo_kind as uapi Alexei Starovoitov
2021-11-24 6:01 ` [PATCH v4 bpf-next 05/16] bpf: Pass a set of bpf_core_relo-s to prog_load command Alexei Starovoitov
2021-11-24 6:01 ` [PATCH v4 bpf-next 06/16] bpf: Adjust BTF log size limit Alexei Starovoitov
2021-11-24 6:02 ` [PATCH v4 bpf-next 07/16] bpf: Add bpf_core_add_cands() and wire it into bpf_core_apply_relo_insn() Alexei Starovoitov
2021-11-30 1:03 ` Andrii Nakryiko
2021-11-30 3:18 ` Alexei Starovoitov
2021-11-30 4:09 ` Andrii Nakryiko
2021-11-30 5:04 ` Alexei Starovoitov
2021-11-30 5:14 ` Andrii Nakryiko
2021-11-30 23:06 ` Alexei Starovoitov
2021-11-30 23:12 ` Andrii Nakryiko
2021-11-30 5:50 ` Alexei Starovoitov
2021-11-24 6:02 ` [PATCH v4 bpf-next 08/16] libbpf: Use CO-RE in the kernel in light skeleton Alexei Starovoitov
2021-11-30 1:11 ` Andrii Nakryiko [this message]
2021-11-24 6:02 ` [PATCH v4 bpf-next 09/16] libbpf: Support init of inner maps " Alexei Starovoitov
2021-11-24 6:02 ` [PATCH v4 bpf-next 10/16] libbpf: Clean gen_loader's attach kind Alexei Starovoitov
2021-11-30 1:11 ` Andrii Nakryiko
2021-11-24 6:02 ` [PATCH v4 bpf-next 11/16] selftests/bpf: Add lskel version of kfunc test Alexei Starovoitov
2021-11-24 6:02 ` [PATCH v4 bpf-next 12/16] selftests/bpf: Improve inner_map test coverage Alexei Starovoitov
2021-11-24 6:02 ` [PATCH v4 bpf-next 13/16] selftests/bpf: Convert map_ptr_kern test to use light skeleton Alexei Starovoitov
2021-11-24 6:02 ` [PATCH v4 bpf-next 14/16] selftests/bpf: Additional test for CO-RE in the kernel Alexei Starovoitov
2021-11-30 1:13 ` Andrii Nakryiko
2021-11-24 6:02 ` [PATCH v4 bpf-next 15/16] selftests/bpf: Revert CO-RE removal in test_ksyms_weak Alexei Starovoitov
2021-11-24 6:02 ` [PATCH v4 bpf-next 16/16] selftests/bpf: Add CO-RE relocations to verifier scale test Alexei Starovoitov
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=CAEf4Bza-NtGJMEtJ99T_y9FFykXHsVwwjqYZ_aFp6+M1Sqfsng@mail.gmail.com \
--to=andrii.nakryiko@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.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 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).