From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Stephen Brennan <stephen.s.brennan@oracle.com>
Cc: bpf@vger.kernel.org, dwarves@vger.kernel.org,
linux-debuggers@vger.kernel.org,
Alan Maguire <alan.maguire@oracle.com>
Subject: Re: [PATCH dwarves v4 0/4] Emit global variables in BTF
Date: Fri, 4 Oct 2024 18:01:46 -0300 [thread overview]
Message-ID: <ZwBXuqV4rbNPB5T6@x1> (raw)
In-Reply-To: <ZwBXA6VCcyF-0aPb@x1>
On Fri, Oct 04, 2024 at 05:58:48PM -0300, Arnaldo Carvalho de Melo wrote:
> On Fri, Oct 04, 2024 at 10:26:24AM -0700, Stephen Brennan wrote:
> > Hi all,
> >
> > This is v4 of the series which adds global variables to pahole's generated BTF.
> >
> > Since v3:
> >
> > 1. Gathered Alan's Reviewed-by + Tested-by, and Jiri's Acked-by.
> > 2. Consistently start shndx loops at 1, and use size_t.
> > 3. Since patch 1 of v3 was already applied, I dropped it out of this series.
> >
> > v3: https://lore.kernel.org/dwarves/20241002235253.487251-1-stephen.s.brennan@oracle.com/
> > v2: https://lore.kernel.org/dwarves/20240920081903.13473-1-stephen.s.brennan@oracle.com/
> > v1: https://lore.kernel.org/dwarves/20240912190827.230176-1-stephen.s.brennan@oracle.com/
> >
> > Thanks everyone for your review, tests, and consideration!
>
> Looks ok, I run the existing regression tests:
>
> acme@x1:~/git/pahole$ tests/tests
> 1: Validation of BTF encoding of functions; this may take some time: Ok
> 2: Pretty printing of files using DWARF type information: Ok
> 3: Parallel reproducible DWARF Loading/Serial BTF encoding: Ok
> /home/acme/git/pahole
> acme@x1:~/git/pahole$
>
> And now I'm building a kernel with clang + Thin LTO + Rust enabled in
> the kernel to test other fixes I have merged and doing that with your
> patch series.
>
> Its all in the next branch and will move to master later today or
> tomorrow when I finish the clang+LTO+Rust tests.
Ah, please consider looking at the test/ scripts and try to write a
simple test that will encode global vars from the running kernel and
then use bpftool to dump them and look for some of the well known kernel
global variables being encoded to match expectations, so that we have
this feature continuously tested vai tests/tests.
If now the increase in size due to global vars is of N%, please consider
checking if that is off by some unreasonable margin, etc.
Thanks!
- Arnaldo
next prev parent reply other threads:[~2024-10-04 21:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 17:26 [PATCH dwarves v4 0/4] Emit global variables in BTF Stephen Brennan
2024-10-04 17:26 ` [PATCH dwarves v4 1/4] btf_encoder: stop indexing symbols for VARs Stephen Brennan
2024-10-04 17:26 ` [PATCH dwarves v4 2/4] btf_encoder: explicitly check addr/size for u32 overflow Stephen Brennan
2024-10-04 17:26 ` [PATCH dwarves v4 3/4] btf_encoder: allow encoding VARs from many sections Stephen Brennan
2024-10-04 17:26 ` [PATCH dwarves v4 4/4] pahole: add global_var BTF feature Stephen Brennan
2024-10-04 20:58 ` [PATCH dwarves v4 0/4] Emit global variables in BTF Arnaldo Carvalho de Melo
2024-10-04 21:01 ` Arnaldo Carvalho de Melo [this message]
2024-10-07 17:12 ` Andrii Nakryiko
2024-10-07 17:24 ` Stephen Brennan
2024-10-07 18:48 ` Arnaldo Carvalho de Melo
2024-10-07 19:00 ` Arnaldo Carvalho de Melo
2024-10-07 21:46 ` 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=ZwBXuqV4rbNPB5T6@x1 \
--to=acme@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=bpf@vger.kernel.org \
--cc=dwarves@vger.kernel.org \
--cc=linux-debuggers@vger.kernel.org \
--cc=stephen.s.brennan@oracle.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).