From: Jiri Olsa <olsajiri@gmail.com>
To: Alan Maguire <alan.maguire@oracle.com>
Cc: acme@kernel.org, dwarves@vger.kernel.org, eddyz87@gmail.com,
olsajiri@gmail.com, shung-hsi.yu@suse.com, jirislaby@kernel.org,
sedat.dilek@gmail.com, w@1wt.eu
Subject: Re: [PATCH v4 dwarves 0/2] fixes for memory optimized BTF
Date: Mon, 30 Sep 2024 13:20:11 +0200 [thread overview]
Message-ID: <ZvqJawSN_UVwQdAc@krava> (raw)
In-Reply-To: <20240930081725.2465825-1-alan.maguire@oracle.com>
On Mon, Sep 30, 2024 at 09:17:23AM +0100, Alan Maguire wrote:
> This series is identical in effect to [1], it is simply applied
> on top of the "next" branch which now includes v2 of the series.
>
> Patch 1 fixes issues identified in code review around use of
> func->state, strncpy issues.
>
> Patch 2 speeds up the btf_functions.sh test by reducing the
> number of greps/pipes, shaving ~1 minute off execution time.
>
> [1] https://lore.kernel.org/dwarves/20240925091734.1943742-1-alan.maguire@oracle.com/
>
> Changes since v2:
>
> - fixed checks of func->state since it is always non-NULL and removed
> now-unneeded fields from dwarves.h; added assertions that either
> ELF or DWARF data is present for func encoding (Jiri, patch 1)
lgtm
Acked-by: Jiri Olsa <jolsa@kernel.org>
jirka
> - fixed strncpy() issues, improved equality comparions between types
> (Eduard, patch 1)
> - reworked btf_functions test to minimize overheads (patch 2)
>
> Changes since RFC:
>
> - fixed free issues (Jiri, patch 1)
> - embed func state into struct elf_function as each function
> has state, and we can use the stack for state comparison
> avoiding the cost of additional allocations (patch 1)
> - fix an intermittent coredump that resulted from using
> btf__str_by_offset() string in adding function prototype;
> needing more space could sometimes result in strset memory
> movement which would in turn invalidate the char * string,
> so copy it to a char array for param name/tag value encoding
> (patch 1)
> - improve logging of decision to skip functions so that we can
> gather that info more easily for testing in patch 3
> - added new option to pfunct to show all instances of a function
> prototype and - if no function is specified - use the stealer
> to dump out all prototypes more rapidly to aid quicker testing
> - added test covering BTF function generation, checking that
> DWARF/BTF are consistent and that for skipped functions the
> skip rationale was valid (Jiri, patch 3)
>
> Alan Maguire (2):
> btf_encoder: fix strncpy issues, other issues identified in code
> review
> tests: improve btf_functions.sh by reducing greps/pipes
>
> btf_encoder.c | 68 ++++++++++++++++++++++++++++--------------
> tests/btf_functions.sh | 22 +++++---------
> 2 files changed, 54 insertions(+), 36 deletions(-)
>
> --
> 2.43.5
>
next prev parent reply other threads:[~2024-09-30 11:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 8:17 [PATCH v4 dwarves 0/2] fixes for memory optimized BTF Alan Maguire
2024-09-30 8:17 ` [PATCH v4 dwarves 1/2] btf_encoder: fix strncpy issues, other issues identified in code review Alan Maguire
2024-09-30 8:17 ` [PATCH v4 dwarves 2/2] tests: improve btf_functions.sh by reducing greps/pipes Alan Maguire
2024-09-30 11:20 ` Jiri Olsa [this message]
2024-09-30 14:34 ` [PATCH v4 dwarves 0/2] fixes for memory optimized BTF Arnaldo Carvalho de Melo
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=ZvqJawSN_UVwQdAc@krava \
--to=olsajiri@gmail.com \
--cc=acme@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=dwarves@vger.kernel.org \
--cc=eddyz87@gmail.com \
--cc=jirislaby@kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=shung-hsi.yu@suse.com \
--cc=w@1wt.eu \
/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.