[EXTERNAL] [PATCH v3 4/6] trace: support dumping binary inside a struct
Sunil Kumar Kori
skori at marvell.com
Tue Feb 11 09:52:37 CET 2025
> diff --git a/lib/eal/common/eal_common_trace_ctf.c
> b/lib/eal/common/eal_common_trace_ctf.c
> index 6bc8bb9036..d9b307e076 100644
> --- a/lib/eal/common/eal_common_trace_ctf.c
> +++ b/lib/eal/common/eal_common_trace_ctf.c
> @@ -378,6 +378,9 @@ char *trace_metadata_fixup_field(const char *field)
> "->",
> "*",
> " ",
> + "&",
> + "(",
> + ")",
Adding brackets makes token names a bit complex. Same name is used in metadata
file to dump the traces to the user. With this complex name, user might not
understand the purpose of that information.
For example, _conf_src_port_pcie_sizeof_uint64_t_ is created in metafile and same will be dumped. But with this
User might not get that which information is provided.
This is the reason; we followed the existing naming convention which is user friendly.
> };
> const char *ctf_reserved_words[] = {
> "align",
> --
> 2.48.1
More information about the dev
mailing list