BPF List
 help / color / mirror / Atom feed
From: Alan Maguire <alan.maguire@oracle.com>
To: Ihor Solodrai <ihor.solodrai@pm.me>, bpf@vger.kernel.org
Cc: andrii@kernel.org, ast@kernel.org, daniel@iogearbox.net,
	eddyz87@gmail.com, mykolal@fb.com, jose.marchesi@oracle.com
Subject: Re: [PATCH bpf-next 2/5] libbpf: check the kflag of type tags in btf_dump
Date: Wed, 22 Jan 2025 10:57:16 +0000	[thread overview]
Message-ID: <6aa763ab-35fa-49a5-970a-0bd28a167daa@oracle.com> (raw)
In-Reply-To: <20250122025308.2717553-3-ihor.solodrai@pm.me>

On 22/01/2025 02:53, Ihor Solodrai wrote:
> If the kflag is set for a BTF type tag, then the tag represents an
> arbitrary __attribute__. Change btf_dump accordingly.
> 
> Signed-off-by: Ihor Solodrai <ihor.solodrai@pm.me>

Reviewed-by: Alan Maguire <alan.maguire@oracle.com>

> ---
>  tools/lib/bpf/btf_dump.c | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/tools/lib/bpf/btf_dump.c b/tools/lib/bpf/btf_dump.c
> index a3fc6908f6c9..460c3e57fadb 100644
> --- a/tools/lib/bpf/btf_dump.c
> +++ b/tools/lib/bpf/btf_dump.c
> @@ -1494,7 +1494,10 @@ static void btf_dump_emit_type_chain(struct btf_dump *d,
>  		case BTF_KIND_TYPE_TAG:
>  			btf_dump_emit_mods(d, decls);
>  			name = btf_name_of(d, t->name_off);
> -			btf_dump_printf(d, " __attribute__((btf_type_tag(\"%s\")))", name);
> +			if (btf_kflag(t))
> +				btf_dump_printf(d, " __attribute__((%s))", name);
> +			else
> +				btf_dump_printf(d, " __attribute__((btf_type_tag(\"%s\")))", name);
>  			break;
>  		case BTF_KIND_ARRAY: {
>  			const struct btf_array *a = btf_array(t);


  reply	other threads:[~2025-01-22 10:57 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 [this message]
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
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=6aa763ab-35fa-49a5-970a-0bd28a167daa@oracle.com \
    --to=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=ihor.solodrai@pm.me \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox