From: Eduard Zingerman <eddyz87@gmail.com>
To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
Cc: dwarves@vger.kernel.org, bpf@vger.kernel.org, kernel-team@fb.com,
ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
yhs@fb.com, jose.marchesi@oracle.com, david.faust@oracle.com,
alan.maguire@oracle.com
Subject: Re: [PATCH dwarves v2 1/5] fprintf: Correct names for types with btf_type_tag attribute
Date: Tue, 28 Mar 2023 18:30:05 +0300 [thread overview]
Message-ID: <50a160d802ad3f84e91cf05c8f541e0c2e388fc8.camel@gmail.com> (raw)
In-Reply-To: <ZCMHKFdmjVpOSNsJ@kernel.org>
On Tue, 2023-03-28 at 12:26 -0300, Arnaldo Carvalho de Melo wrote:
[...]
> Sure, but look:
>
> > > - struct qdisc_size_table * stab; /* 32 8 */
> > > + struct qdisc_size_table stab; /* 32 8 */
>
> Its the DW_TAG_pointer_type that is getting lost somehow:
>
> <1><b0af32>: Abbrev Number: 81 (DW_TAG_structure_type)
> <b0af33> DW_AT_name : (indirect string, offset: 0xe825): Qdisc
> <b0af37> DW_AT_byte_size : 384
> <b0af39> DW_AT_decl_file : 223
> <b0af3a> DW_AT_decl_line : 72
>
> <SNIP>
>
> <2><b0af77>: Abbrev Number: 65 (DW_TAG_member)
> <b0af78> DW_AT_name : (indirect string, offset: 0x4745ff): stab
> <b0af7c> DW_AT_type : <0xb0b76b>
> <b0af80> DW_AT_decl_file : 223
> <b0af81> DW_AT_decl_line : 99
> <b0af82> DW_AT_data_member_location: 32
>
> <SNIP>
>
> <1><b0b76b>: Abbrev Number: 61 (DW_TAG_pointer_type)
> <b0b76c> DW_AT_type : <0xb0b77a>
> <2><b0b770>: Abbrev Number: 62 (User TAG value: 0x6000)
> <b0b771> DW_AT_name : (indirect string, offset: 0x378): btf_type_tag
> <b0b775> DW_AT_const_value : (indirect string, offset: 0x6e93): rcu
> <2><b0b779>: Abbrev Number: 0
> <1><b0b77a>: Abbrev Number: 69 (DW_TAG_structure_type)
> <b0b77b> DW_AT_name : (indirect string, offset: 0x6e5ed): qdisc_size_table
> <b0b77f> DW_AT_byte_size : 64
> <b0b780> DW_AT_decl_file : 223
> <b0b781> DW_AT_decl_line : 56
>
>
> So it's all there in the DWARF info:
>
> b0af77 has type 0xb0b76b which is a DW_TAG_pointer_type that has type
> 0xb0b77a, that is DW_TAG_structure_type.
>
> Now lets see how this was encoded into BTF:
>
> [4725] STRUCT 'Qdisc' size=384 vlen=28
> <SNIP>
> 'stab' type_id=4790 bits_offset=256
> <SNIP>
> [4790] PTR '(anon)' type_id=4789
> <SNIP>
> [4789] TYPE_TAG 'rcu' type_id=4791
> <SNIP>
> [4791] STRUCT 'qdisc_size_table' size=64 vlen=5
> 'rcu' type_id=320 bits_offset=0
> 'list' type_id=87 bits_offset=128
> 'szopts' type_id=4792 bits_offset=256
> 'refcnt' type_id=16 bits_offset=448
> 'data' type_id=4659 bits_offset=480
>
> So it all seems ok, we should keep all the info and teach fprintf to
> handle TYPE_TAG.
>
> Which you tried, but somehow the '*' link is missing.
Yep, thanks a lot for the analysis, I will take a look.
Hopefully will send v2 tomorrow.
>
> - Arnaldo
next prev parent reply other threads:[~2023-03-28 15:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 23:04 [PATCH dwarves v2 0/5] Support for new btf_type_tag encoding Eduard Zingerman
2023-03-14 23:04 ` [PATCH dwarves v2 1/5] fprintf: Correct names for types with btf_type_tag attribute Eduard Zingerman
2023-03-27 11:46 ` Arnaldo Carvalho de Melo
2023-03-27 12:10 ` Eduard Zingerman
2023-03-27 12:55 ` Arnaldo Carvalho de Melo
2023-03-28 12:40 ` Arnaldo Carvalho de Melo
2023-03-28 13:40 ` Eduard Zingerman
2023-03-28 13:59 ` Arnaldo Carvalho de Melo
2023-03-28 14:08 ` Eduard Zingerman
2023-03-28 15:26 ` Arnaldo Carvalho de Melo
2023-03-28 15:30 ` Eduard Zingerman [this message]
2023-03-28 21:17 ` Arnaldo Carvalho de Melo
2023-03-29 15:36 ` Eduard Zingerman
2023-03-29 15:43 ` Arnaldo Carvalho de Melo
2023-03-29 16:02 ` Eduard Zingerman
2023-03-30 11:29 ` Arnaldo Carvalho de Melo
2023-03-30 12:34 ` Eduard Zingerman
2023-03-14 23:04 ` [PATCH dwarves v2 2/5] btf_loader: A hack for BTF import of btf_type_tag attributes Eduard Zingerman
2023-03-14 23:04 ` [PATCH dwarves v2 3/5] dwarf_loader: Consolidate llvm_annotation and btf_type_tag_type Eduard Zingerman
2023-03-14 23:04 ` [PATCH dwarves v2 4/5] dwarf_loader: Track unspecified types in a separate list Eduard Zingerman
2023-03-14 23:04 ` [PATCH dwarves v2 5/5] dwarf_loader: Support for btf:type_tag 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=50a160d802ad3f84e91cf05c8f541e0c2e388fc8.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=arnaldo.melo@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=david.faust@oracle.com \
--cc=dwarves@vger.kernel.org \
--cc=jose.marchesi@oracle.com \
--cc=kernel-team@fb.com \
--cc=yhs@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