From: Jiri Olsa <olsajiri@gmail.com>
To: Alan Maguire <alan.maguire@oracle.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
quentin@isovalent.com, eddyz87@gmail.com, martin.lau@linux.dev,
song@kernel.org, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, bpf@vger.kernel.org
Subject: Re: [PATCH v3 bpf-next 09/17] bpf: switch to --btf_features, add crc,kind_layout features
Date: Sun, 12 Nov 2023 06:57:04 +0100 [thread overview]
Message-ID: <ZVBpMLvqhrFpnd3d@krava> (raw)
In-Reply-To: <20231110110304.63910-10-alan.maguire@oracle.com>
On Fri, Nov 10, 2023 at 11:02:56AM +0000, Alan Maguire wrote:
> For pahole v1.26 and later, --btf_features is used to specify BTF
> features for encoding. Since it tolerates unknown features, no
> further version checking will be needed when adding new features.
> Add crc, kind_layout features.
hi,
this commit got merged:
72d091846de9 kbuild: avoid too many execution of scripts/pahole-flags.sh
so this change needs rebase
jirka
>
> Signed-off-by: Alan Maguire <alan.maguire@oracle.com>
> ---
> scripts/pahole-flags.sh | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/scripts/pahole-flags.sh b/scripts/pahole-flags.sh
> index 728d55190d97..30a3e270308b 100755
> --- a/scripts/pahole-flags.sh
> +++ b/scripts/pahole-flags.sh
> @@ -26,5 +26,8 @@ fi
> if [ "${pahole_ver}" -ge "125" ]; then
> extra_paholeopt="${extra_paholeopt} --skip_encoding_btf_inconsistent_proto --btf_gen_optimized"
> fi
> +if [ "${pahole_ver}" -ge "126" ]; then
> + extra_paholeopt="-j --lang_exclude=rust --btf_features=encode_force,var,float,decl_tag,type_tag,enum64,optimized_func,consistent_func,crc,kind_layout"
> +fi
>
> echo ${extra_paholeopt}
> --
> 2.31.1
>
next prev parent reply other threads:[~2023-11-12 5:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 11:02 [PATCH v3 bpf-next 00/17] Add kind layout, CRCs to BTF Alan Maguire
2023-11-10 11:02 ` [PATCH v3 bpf-next 01/17] btf: add kind layout encoding, crcs to UAPI Alan Maguire
2023-11-10 11:02 ` [PATCH v3 bpf-next 02/17] libbpf: support kind layout section handling in BTF Alan Maguire
2023-11-10 11:02 ` [PATCH v3 bpf-next 03/17] libbpf: use kind layout to compute an unknown kind size Alan Maguire
2023-11-10 11:02 ` [PATCH v3 bpf-next 04/17] libbpf: add kind layout encoding, crc support Alan Maguire
2023-11-10 11:02 ` [PATCH v3 bpf-next 05/17] libbpf: BTF validation can use kind layout for unknown kinds Alan Maguire
2023-11-10 11:02 ` [PATCH v3 bpf-next 06/17] btf: support kernel parsing of BTF with kind layout Alan Maguire
2023-11-10 11:02 ` [PATCH v3 bpf-next 07/17] bpf: add BTF CRC verification where present Alan Maguire
2023-11-10 11:02 ` [PATCH v3 bpf-next 08/17] bpf: verify base BTF CRC to ensure it matches module BTF Alan Maguire
2023-11-10 11:02 ` [PATCH v3 bpf-next 09/17] bpf: switch to --btf_features, add crc,kind_layout features Alan Maguire
2023-11-12 5:57 ` Jiri Olsa [this message]
2023-11-12 12:55 ` Alan Maguire
2023-11-10 11:02 ` [PATCH v3 bpf-next 10/17] bpftool: add BTF dump "format meta" to dump header/metadata Alan Maguire
2023-11-10 11:02 ` [PATCH v3 bpf-next 11/17] bpftool: update doc to describe bpftool btf dump .. format meta Alan Maguire
2023-11-10 11:02 ` [PATCH v3 bpf-next 12/17] selftests/bpf: test kind encoding/decoding Alan Maguire
2023-11-10 11:03 ` [PATCH v3 bpf-next 13/17] bpf: support standalone BTF in modules Alan Maguire
2023-11-10 11:03 ` [PATCH v3 bpf-next 14/17] bpf: allow opt-out from using split BTF for modules Alan Maguire
2023-11-10 11:03 ` [PATCH v3 bpf-next 15/17] selftests/bpf: generalize module load to support specifying a module name Alan Maguire
2023-11-10 11:03 ` [PATCH v3 bpf-next 16/17] selftests/bpf: build separate bpf_testmod module with standalone BTF Alan Maguire
2023-11-10 11:03 ` [PATCH v3 bpf-next 17/17] selftests/bpf: update btf_module test to ensure standalone BTF works Alan Maguire
2023-11-10 16:45 ` [PATCH v3 bpf-next 00/17] Add kind layout, CRCs to BTF Alan Maguire
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=ZVBpMLvqhrFpnd3d@krava \
--to=olsajiri@gmail.com \
--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=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=quentin@isovalent.com \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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.