From: Eduard Zingerman <eddyz87@gmail.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, martin.lau@linux.dev, kernel-team@fb.com,
yonghong.song@linux.dev
Subject: Re: [PATCH bpf-next v1 0/3] veristat: @files-list.txt notation for object files list
Date: Fri, 28 Feb 2025 15:00:45 -0800 [thread overview]
Message-ID: <72b29dccf20ac55e2c1652f9a3ca917719eefdce.camel@gmail.com> (raw)
In-Reply-To: <CAEf4BzY77xkTjKvNE-T0emQWWMuNN-Z6uq16BWs1Waxzx-i-7w@mail.gmail.com>
On Fri, 2025-02-28 at 14:47 -0800, Andrii Nakryiko wrote:
> On Fri, Feb 28, 2025 at 11:13 AM Eduard Zingerman <eddyz87@gmail.com> wrote:
> >
> > A few small veristat improvements:
> > - It is possible to hit command line parameters number limit,
> > e.g. when running veristat for all object files generated for
> > test_progs. This patch-set adds an option to read objects files list
> > from a file.
> > - Correct usage of strerror() function.
> > - Avoid printing log lines to CSV output.
> >
>
> All makes sense, and superficially LGTM, but I'd like Mykyta to take a
> look when he gets a chance, as he's been working with veristat quite a
> lot recently.
Thanks. I'll wait for Mykytas comments before sending v2 with -err.
> One thing I wanted to propose/ask. Do you think it would be useful to
> allow <object>:<program> pattern to be specified to allow picking just
> one program out of the object file? I normally do `veristat <object>
> -f<program>` for this, but being able to do `veristat <obj1>:<prog1>
> <obj2>:<prog2> ...` seems useful, no? (-f<program> would apply to all
> objects, btw, which isn't a big problem in practice, but still). Oh,
> and we could allow globbing in `veristat <obj>:<blah*>`.
>
> Thoughts?
Tbh I don't remember myself ever needing this, -f was sufficient.
Every time I used -f, it was to do <object>:<program> for a single program.
On the other hand, this looks like a nice generalization.
This does not seem to be too complicated, so I'd say lets add it,
the use case will find us eventually.
One thing I do want is multi-threading.
E.g. it takes about 2 minutes to process all .bpf.o from
selftests/bpf/cpuv4/, and it can be slashed to 10s of seconds.
Per-object this should be straightforward.
Per-program this would need to wait for Mykyta's work on prepare object,
as far as I understand.
I can add the per-object version over the weekend if you are ok with
such granularity.
next prev parent reply other threads:[~2025-02-28 23:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 19:12 [PATCH bpf-next v1 0/3] veristat: @files-list.txt notation for object files list Eduard Zingerman
2025-02-28 19:12 ` [PATCH bpf-next v1 1/3] " Eduard Zingerman
2025-02-28 19:12 ` [PATCH bpf-next v1 2/3] veristat: strerror expects positive number (errno) Eduard Zingerman
2025-02-28 22:44 ` Andrii Nakryiko
2025-02-28 22:46 ` Eduard Zingerman
2025-02-28 19:12 ` [PATCH bpf-next v1 3/3] veristat: report program type guess results to sdterr Eduard Zingerman
2025-02-28 22:47 ` [PATCH bpf-next v1 0/3] veristat: @files-list.txt notation for object files list Andrii Nakryiko
2025-02-28 23:00 ` Eduard Zingerman [this message]
2025-02-28 23:10 ` Andrii Nakryiko
2025-02-28 23:33 ` Mykyta Yatsenko
2025-03-01 0:03 ` Eduard Zingerman
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=72b29dccf20ac55e2c1652f9a3ca917719eefdce.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=martin.lau@linux.dev \
--cc=yonghong.song@linux.dev \
/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.