bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin KaFai Lau <kafai@fb.com>
To: Grant Seltzer Richman <grantseltzer@gmail.com>
Cc: <andrii@kernel.org>, <daniel@iogearbox.net>,
	<songliubraving@fb.com>, <john.fastabend@gmail.com>,
	<kpsingh@kernel.org>, <bpf@vger.kernel.org>
Subject: Re: [PATCH] add CONFIG_DEBUG_INFO_BTF check to bpftool feature command
Date: Sat, 20 Feb 2021 14:50:18 -0800	[thread overview]
Message-ID: <20210220225018.oezm23abceggcy4f@kafai-mbp> (raw)
In-Reply-To: <CAO658oUwgX-aVutTn+3f=gZ5ZfdTuHUakAetfpXo_LN=Va=SyA@mail.gmail.com>

On Fri, Feb 19, 2021 at 05:43:00PM -0500, Grant Seltzer Richman wrote:
> This adds the CONFIG_DEBUG_INFO_BTF kernel compile option to output of
> the bpftool feature command. This is relevant for developers that want
> to use libbpf to account for data structure definition differences
> between kernels.
> 
> Signed-off-by: grantseltzer <grantseltzer@gmail.com>
> ---
>  tools/bpf/bpftool/feature.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/tools/bpf/bpftool/feature.c b/tools/bpf/bpftool/feature.c
> index 359960a8f..34343e7fa 100644
> --- a/tools/bpf/bpftool/feature.c
> +++ b/tools/bpf/bpftool/feature.c
> @@ -336,6 +336,8 @@ static void probe_kernel_image_config(const char
> *define_prefix)
>                 { "CONFIG_BPF_JIT", },
>                 /* Avoid compiling eBPF interpreter (use JIT only) */
>                 { "CONFIG_BPF_JIT_ALWAYS_ON", },
> +               /* Enable using BTF debug information */
> +               { "CONFIG_DEBUG_INFO_BTF", },
> 
>                 /* cgroups */
>                 { "CONFIG_CGROUPS", },
> --
> 2.29.2
> 
> On Fri, Feb 19, 2021 at 5:36 PM Martin KaFai Lau <kafai@fb.com> wrote:
> >
> > There is no description.  Please provide a commit message.
> >
> > On Fri, Feb 19, 2021 at 10:21:35PM +0000, grantseltzer wrote:
> > > Signed-off-by: grantseltzer <grantseltzer@gmail.com>
> > > ---
> > >  tools/bpf/bpftool/feature.c | 2 ++
> > >  1 file changed, 2 insertions(+)
> > >
> > > diff --git a/tools/bpf/bpftool/feature.c b/tools/bpf/bpftool/feature.c
> > > index 359960a8f..34343e7fa 100644
> > > --- a/tools/bpf/bpftool/feature.c
> > > +++ b/tools/bpf/bpftool/feature.c
> > > @@ -336,6 +336,8 @@ static void probe_kernel_image_config(const char *define_prefix)
> > >               { "CONFIG_BPF_JIT", },
> > >               /* Avoid compiling eBPF interpreter (use JIT only) */
> > >               { "CONFIG_BPF_JIT_ALWAYS_ON", },
> > > +             /* Enable using BTF debug information */
> > > +             { "CONFIG_DEBUG_INFO_BTF", },
> > >
> > >               /* cgroups */
> > >               { "CONFIG_CGROUPS", },
I don't think this old reference "> >" part can be applied.
Please resubmit a clean patch instead of replying to the
old one.  Documentation/process/submitting-patches.rst has
details on the how-tos.

It is not a bug fix, so it belongs to bpf-next
(Documentation/bpf/bpf_devel_QA.rst).
Please tag it with bpf-next.  The next revision will be v2,
sample commands would be:
git format-patch --subject-prefix='PATCH v2 bpf-next' ...
./scripts/checkpatch.pl ...
git send-email ...

      reply	other threads:[~2021-02-20 22:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-19 22:21 [PATCH] add CONFIG_DEBUG_INFO_BTF check to bpftool feature command grantseltzer
2021-02-19 22:36 ` Martin KaFai Lau
2021-02-19 22:43   ` Grant Seltzer Richman
2021-02-20 22:50     ` Martin KaFai Lau [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=20210220225018.oezm23abceggcy4f@kafai-mbp \
    --to=kafai@fb.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=grantseltzer@gmail.com \
    --cc=john.fastabend@gmail.com \
    --cc=kpsingh@kernel.org \
    --cc=songliubraving@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).