bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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>,
	Networking <netdev@vger.kernel.org>, bpf <bpf@vger.kernel.org>,
	Kernel Team <kernel-team@fb.com>
Subject: Re: [PATCH bpf-next 0/4] libbpf: Move CO-RE logic into separate file.
Date: Mon, 26 Jul 2021 12:37:56 -0700	[thread overview]
Message-ID: <CAEf4Bza3nAgUVdaP6sh9XG4oMdawCp55UeAB3Lgjf9opCw_UnA@mail.gmail.com> (raw)
In-Reply-To: <20210721000822.40958-1-alexei.starovoitov@gmail.com>

On Tue, Jul 20, 2021 at 5:08 PM Alexei Starovoitov
<alexei.starovoitov@gmail.com> wrote:
>
> From: Alexei Starovoitov <ast@kernel.org>
>
> Split CO-RE processing logic from libbpf into separate file
> with an interface that doesn't dependend on libbpf internal details.
> As the next step relo_core.c will be compiled with libbpf and with the kernel.
> The _internal_ interface between libbpf/CO-RE and kernel/CO-RE will be:
> int bpf_core_apply_relo_insn(const char *prog_name, struct bpf_insn *insn,
>                              int insn_idx,
>                              const struct bpf_core_relo *relo,
>                              int relo_idx,
>                              const struct btf *local_btf,
>                              struct bpf_core_cand_list *cands);
> where bpf_core_relo and bpf_core_cand_list are simple types
> prepared by kernel and libbpf.
>
> Though diff stat shows a lot of lines inserted/deleted they are moved lines.
> Pls review with diff.colorMoved.
>
> Alexei Starovoitov (4):
>   libbpf: Cleanup the layering between CORE and bpf_program.
>   libbpf: Split bpf_core_apply_relo() into bpf_program indepdent helper.
>   libbpf: Move CO-RE types into relo_core.h.
>   libbpf: Split CO-RE logic into relo_core.c.
>

LGTM. Applied to bpf-next, fixed typo in patch 3 subject, and also
made few adjustments. Let me know if you object to any of them:

1. I felt like the original copyright year should be preserved when
moving code into a new file, so I've changed relo_core.h's year to
2019. Hope that's fine.
2. relo_core.c didn't have a Copyright line, so I added the /*
Copyright (c) 2019 Facebook */ as well.
3. I trimmed down the list of #includes in core_relo.c, because most
of them were absolutely irrelevant and just preserved as-is from
libbpf.c Everything seems to compile just fine without those.

>  tools/lib/bpf/Build             |    2 +-
>  tools/lib/bpf/libbpf.c          | 1344 +------------------------------
>  tools/lib/bpf/libbpf_internal.h |   81 +-
>  tools/lib/bpf/relo_core.c       | 1326 ++++++++++++++++++++++++++++++
>  tools/lib/bpf/relo_core.h       |  102 +++
>  5 files changed, 1473 insertions(+), 1382 deletions(-)
>  create mode 100644 tools/lib/bpf/relo_core.c
>  create mode 100644 tools/lib/bpf/relo_core.h
>
> --
> 2.30.2
>

  parent reply	other threads:[~2021-07-26 19:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-21  0:08 [PATCH bpf-next 0/4] libbpf: Move CO-RE logic into separate file Alexei Starovoitov
2021-07-21  0:08 ` [PATCH bpf-next 1/4] libbpf: Cleanup the layering between CORE and bpf_program Alexei Starovoitov
2021-07-21  0:08 ` [PATCH bpf-next 2/4] libbpf: Split bpf_core_apply_relo() into bpf_program indepdent helper Alexei Starovoitov
2021-07-21  0:08 ` [PATCH bpf-next 3/4] libbpf: Move CO-RE types into relo_core.h Alexei Starovoitov
2021-07-21  0:08 ` [PATCH bpf-next 4/4] libbpf: Split CO-RE logic into relo_core.c Alexei Starovoitov
2021-07-22 16:02 ` [PATCH bpf-next 0/4] libbpf: Move CO-RE logic into separate file Toke Høiland-Jørgensen
2021-07-24  0:23   ` Alexei Starovoitov
2021-07-26 19:37 ` Andrii Nakryiko [this message]
2021-07-28  4:49   ` Alexei Starovoitov
2021-07-29 18:43     ` Andrii Nakryiko

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=CAEf4Bza3nAgUVdaP6sh9XG4oMdawCp55UeAB3Lgjf9opCw_UnA@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 \
    --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).