From: Ihor Solodrai <ihor.solodrai@linux.dev>
To: Alan Maguire <alan.maguire@oracle.com>, bpf@vger.kernel.org
Cc: andrii@kernel.org, ast@kernel.org, daniel@iogearbox.net,
eddyz87@gmail.com, mykolal@fb.com, jose.marchesi@oracle.com,
Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: [PATCH bpf-next 0/5] BTF: arbitrary __attribute__ encoding
Date: Mon, 27 Jan 2025 12:51:02 -0800 [thread overview]
Message-ID: <6decc31d-838f-4caa-957c-9230a970d01e@linux.dev> (raw)
In-Reply-To: <4bc39acd-e7ce-44e1-b7c7-ffbeb1ecb4f1@oracle.com>
On 1/22/25 2:13 AM, Alan Maguire wrote:
> On 22/01/2025 02:53, Ihor Solodrai wrote:
>> This patch series extends BPF Type Format (BTF) to support arbitrary
>> __attribute__ encoding.
>>
>> Setting the kind_flag to 1 in BTF type tags and decl tags now changes
>> the meaning for the encoded tag, in particular with respect to
>> btf_dump in libbpf.
>>
>> If the kflag is set, then the string encoded by the tag represents the
>> full attribute-list of an attribute specifier [1].
>>
>> This feature will allow extending tools such as pahole and bpftool to
>> capture and use more granular type information, and make it easier to
>> manage compatibility between clang and gcc BPF compilers.
>>
>
> sounds good! So presumably pahole will then have a "full_attribute" or
> similar BTF feature that will only do full attribute encoding for
> kernels that expect the kind flag to be set? Otherwise we'll run the
> risk of generating invalid BTF for older kernels with newer pahole
> (since those older kernels will fail to verify tags with a kind flag
set).
Hi Alan. Sorry I missed this message on the first pass.
Yes, this BTF extension enables pahole to encode any __attribute__ in
BTF. There is already a use case for that, which led me to this patch
series: expressing bpf_arena tags in vmlinux.h.
As to "full_attribute"-like feature in pahole, my intuition is that
it's a significant chunk of work, and it might not be necessary in the
near future. But with these changes in BTF it at least becomes a
possibility. And you're right, it will have to be an optional feature.
>
> Thanks!
>
> Alan
>
>> [1] https://gcc.gnu.org/onlinedocs/gcc-13.2.0/gcc/Attribute-Syntax.html
>>
>> Ihor Solodrai (5):
>> libbpf: introduce kflag for type_tags and decl_tags in BTF
>> libbpf: check the kflag of type tags in btf_dump
>> selftests/bpf: add a btf_dump test for type_tags
>> bpf: allow kind_flag for BTF type and decl tags
>> selftests/bpf: add a BTF verification test for kflagged type_tag
>>
>> Documentation/bpf/btf.rst | 27 +++-
>> kernel/bpf/btf.c | 7 +-
>> tools/include/uapi/linux/btf.h | 3 +-
>> tools/lib/bpf/btf.c | 87 +++++++---
>> tools/lib/bpf/btf.h | 3 +
>> tools/lib/bpf/btf_dump.c | 5 +-
>> tools/lib/bpf/libbpf.map | 2 +
>> tools/testing/selftests/bpf/prog_tests/btf.c | 23 ++-
>> .../selftests/bpf/prog_tests/btf_dump.c | 148 +++++++++++++-----
>> tools/testing/selftests/bpf/test_btf.h | 6 +
>> 10 files changed, 234 insertions(+), 77 deletions(-)
>>
>
next prev parent reply other threads:[~2025-01-27 20:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 2:53 [PATCH bpf-next 0/5] BTF: arbitrary __attribute__ encoding Ihor Solodrai
2025-01-22 2:53 ` [PATCH bpf-next 1/5] libbpf: introduce kflag for type_tags and decl_tags in BTF Ihor Solodrai
2025-01-22 10:56 ` Alan Maguire
2025-01-22 18:22 ` Ihor Solodrai
2025-01-22 22:02 ` Andrii Nakryiko
2025-01-22 2:53 ` [PATCH bpf-next 2/5] libbpf: check the kflag of type tags in btf_dump Ihor Solodrai
2025-01-22 10:57 ` Alan Maguire
2025-01-22 2:53 ` [PATCH bpf-next 3/5] selftests/bpf: add a btf_dump test for type_tags Ihor Solodrai
2025-01-23 2:45 ` Eduard Zingerman
2025-01-22 2:53 ` [PATCH bpf-next 4/5] bpf: allow kind_flag for BTF type and decl tags Ihor Solodrai
2025-01-22 11:09 ` Alan Maguire
2025-01-22 18:25 ` Ihor Solodrai
2025-01-22 2:53 ` [PATCH bpf-next 5/5] selftests/bpf: add a BTF verification test for kflagged type_tag Ihor Solodrai
2025-01-22 10:13 ` [PATCH bpf-next 0/5] BTF: arbitrary __attribute__ encoding Alan Maguire
2025-01-27 20:51 ` Ihor Solodrai [this message]
2025-01-22 11:44 ` Jose E. Marchesi
2025-01-22 18:06 ` Ihor Solodrai
2025-01-22 19:47 ` Jose E. Marchesi
2025-01-22 20:38 ` Ihor Solodrai
2025-01-22 21:52 ` Andrii Nakryiko
2025-01-22 22:44 ` Jose E. Marchesi
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=6decc31d-838f-4caa-957c-9230a970d01e@linux.dev \
--to=ihor.solodrai@linux.dev \
--cc=acme@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=jose.marchesi@oracle.com \
--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 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.