public inbox for dwarves@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <olsajiri@gmail.com>
To: Ihor Solodrai <ihor.solodrai@pm.me>
Cc: dwarves@vger.kernel.org, acme@kernel.org, bpf@vger.kernel.org,
	alan.maguire@oracle.com, eddyz87@gmail.com, andrii@kernel.org,
	mykolal@fb.com
Subject: Re: [RFC PATCH 0/9] pahole: shared ELF and faster reproducible BTF encoding
Date: Mon, 2 Dec 2024 14:55:44 +0100	[thread overview]
Message-ID: <Z028YOBN_EnUA9Qm@krava> (raw)
In-Reply-To: <20241128012341.4081072-1-ihor.solodrai@pm.me>

On Thu, Nov 28, 2024 at 01:23:44AM +0000, Ihor Solodrai wrote:

SNIP

> Test results for this patch series:
> 
>   1: Validation of BTF encoding of functions; this may take some time: Ok
>   2: Default BTF on a system without BTF: Ok
>   3: Flexible arrays accounting: WARNING: still unsuported BTF_KIND_DECL_TAG(bpf_fastcall) for bpf_cast_to_kern_ctx already with attribute (bpf_kfunc), ignoring
> WARNING: still unsuported BTF_KIND_DECL_TAG(bpf_fastcall) for bpf_rdonly_cast already with attribute (bpf_kfunc), ignoring
> pahole: type 'nft_pipapo_elem' not found
> pahole: type 'ip6t_standard' not found
> pahole: type 'ip6t_error' not found
> pahole: type 'nft_rbtree_elem' not found
> pahole: type 'nft_rule_dp_last' not found
> pahole: type 'nft_bitmap_elem' not found
> pahole: type 'fuse_direntplus' not found
> pahole: type 'ipt_standard' not found
> pahole: type 'ipt_error' not found
> pahole: type 'tls_rec' not found
> pahole: type 'nft_rhash_elem' not found
> pahole: type 'nft_hash_elem' not found
> Ok
>   4: Pretty printing of files using DWARF type information: Ok
>   5: Parallel reproducible DWARF Loading/Serial BTF encoding: Ok

hi,
when trying selftests with this change, I'm getting wrong .BTF
on bpf selftest bpf_testmod.ko module

$ bpftool btf dump file ./bpf_testmod.ko
Error: failed to load BTF from ./bpf_testmod.ko: Invalid argument

jirka

> 
> 
> [1]: https://lore.kernel.org/dwarves/20241016001025.857970-1-ihor.solodrai@pm.me/
> [2]: https://github.com/theihor/dwarves/pull/3
> [3]: https://lore.kernel.org/dwarves/8678ce40-3ce2-4ece-985b-a40427386d57@oracle.com/
> [4]: https://github.com/acmel/dwarves/compare/master...alan-maguire:dwarves:elf-prep
> [5]: https://github.com/theihor/dwarves/pull/8
> [6]: https://gist.github.com/theihor/f000ce89427828e61fdaa567b332649b
> [7]: https://github.com/theihor/dwarves/pull/8/commits/a7bc67d79d90f98776c6dc5fdaf9f088eb09909d
> 
> 
> Alan Maguire (3):
>   btf_encoder: simplify function encoding
>   btf_encoder: store,use section-relative addresses in ELF function
>     representation
>   btf_encoder: separate elf function, saved function representations
> 
> Ihor Solodrai (6):
>   dwarf_loader: introduce pre_load_module hook to conf_load
>   btf_encoder: introduce elf_functions struct type
>   btf_encoder: collect elf_functions in btf_encoder__pre_load_module
>   btf_encoder: switch to shared elf_functions table
>   btf_encoder: introduce btf_encoding_context
>   pahole: faster reproducible BTF encoding
> 
>  btf_encoder.c  | 661 ++++++++++++++++++++++++++++++-------------------
>  btf_encoder.h  |   6 +
>  dwarf_loader.c |  18 +-
>  dwarves.c      |  47 ++--
>  dwarves.h      |  16 +-
>  pahole.c       | 265 +++++++++-----------
>  6 files changed, 567 insertions(+), 446 deletions(-)
> 
> -- 
> 2.47.0
> 
> 

  parent reply	other threads:[~2024-12-02 13:55 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-28  1:23 [RFC PATCH 0/9] pahole: shared ELF and faster reproducible BTF encoding Ihor Solodrai
2024-11-28  1:23 ` [RFC PATCH 1/9] btf_encoder: simplify function encoding Ihor Solodrai
2024-11-29  8:16   ` Eduard Zingerman
2024-12-02 13:55   ` Jiri Olsa
2024-11-28  1:23 ` [RFC PATCH 2/9] btf_encoder: store,use section-relative addresses in ELF function representation Ihor Solodrai
2024-11-29  9:07   ` Eduard Zingerman
2024-12-02 14:34     ` Alan Maguire
2024-11-28  1:23 ` [RFC PATCH 3/9] btf_encoder: separate elf function, saved function representations Ihor Solodrai
2024-11-29 20:37   ` Eduard Zingerman
2024-12-09 21:19     ` Ihor Solodrai
2024-11-28  1:24 ` [RFC PATCH 4/9] dwarf_loader: introduce pre_load_module hook to conf_load Ihor Solodrai
2024-11-29 21:03   ` Eduard Zingerman
2024-11-28  1:24 ` [RFC PATCH 5/9] btf_encoder: introduce elf_functions struct type Ihor Solodrai
2024-11-29 21:50   ` Eduard Zingerman
2024-11-28  1:24 ` [RFC PATCH 6/9] btf_encoder: collect elf_functions in btf_encoder__pre_load_module Ihor Solodrai
2024-11-29 22:27   ` Eduard Zingerman
2024-11-28  1:24 ` [RFC PATCH 7/9] btf_encoder: switch to shared elf_functions table Ihor Solodrai
2024-11-29 22:35   ` Eduard Zingerman
2024-12-09 23:55     ` Ihor Solodrai
2024-11-28  1:24 ` [RFC PATCH 8/9] btf_encoder: introduce btf_encoding_context Ihor Solodrai
2024-11-29 23:12   ` Eduard Zingerman
2024-11-28  1:24 ` [RFC PATCH 9/9] pahole: faster reproducible BTF encoding Ihor Solodrai
2024-11-30  0:17   ` Eduard Zingerman
2024-12-02 13:55 ` Jiri Olsa [this message]
2024-12-06 18:19   ` [RFC PATCH 0/9] pahole: shared ELF and " Ihor Solodrai
2024-12-06 18:30     ` 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=Z028YOBN_EnUA9Qm@krava \
    --to=olsajiri@gmail.com \
    --cc=acme@kernel.org \
    --cc=alan.maguire@oracle.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=dwarves@vger.kernel.org \
    --cc=eddyz87@gmail.com \
    --cc=ihor.solodrai@pm.me \
    --cc=mykolal@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