From: Jiri Olsa <olsajiri@gmail.com>
To: Alan Maguire <alan.maguire@oracle.com>
Cc: ast@kernel.org, andrii@kernel.org, masahiroy@kernel.org,
daniel@iogearbox.net, nathan@kernel.org, nicolas@fjasle.eu,
martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
yonghong.song@linux.dev, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@google.com, haoluo@google.com,
bpf@vger.kernel.org, linux-kbuild@vger.kernel.org,
asmadeus@codewreck.org
Subject: Re: [PATCH bpf-next] kbuild, bpf: reproducible BTF from pahole when KBUILD_BUILD_TIMESTAMP set
Date: Tue, 2 Jul 2024 01:07:33 +0200 [thread overview]
Message-ID: <ZoM2tY2QdD-41g80@krava> (raw)
In-Reply-To: <20240701173133.3283312-1-alan.maguire@oracle.com>
On Mon, Jul 01, 2024 at 06:31:33PM +0100, Alan Maguire wrote:
> Reproducible builds [1] require that the same source code with
> the same set of tools can build identical objects each time,
> but pahole in parallel mode was non-deterministic in
> BTF generation prior to
>
> dba7b5e ("pahole: Encode BTF serially in a reproducible build")
>
> This was a problem since said BTF is baked into kernels and modules in
> .BTF sections, so parallel pahole was causing non-reproducible binary
> generation. Now with the above commit we have support for parallel
> reproducible BTF generation in pahole.
>
> KBUILD_BUILD_TIMESTAMP is set for reproducible builds, so if it
> is set, add reproducible_build to --btf_features.
>
> [1] Documentation/kbuild/reproducible-builds.rst
>
> Signed-off-by: Alan Maguire <alan.maguire@oracle.com>
makes sense
Acked-by: Jiri Olsa <jolsa@kernel.org>
jirka
> ---
> scripts/Makefile.btf | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/scripts/Makefile.btf b/scripts/Makefile.btf
> index b75f09f3f424..40bb72662967 100644
> --- a/scripts/Makefile.btf
> +++ b/scripts/Makefile.btf
> @@ -21,6 +21,10 @@ else
> # Switch to using --btf_features for v1.26 and later.
> pahole-flags-$(call test-ge, $(pahole-ver), 126) = -j --btf_features=encode_force,var,float,enum64,decl_tag,type_tag,optimized_func,consistent_func,decl_tag_kfuncs
>
> +ifneq ($(KBUILD_BUILD_TIMESTAMP),)
> +pahole-flags-$(call test-ge, $(pahole-ver), 126) += --btf_features=reproducible_build
> +endif
> +
> ifneq ($(KBUILD_EXTMOD),)
> module-pahole-flags-$(call test-ge, $(pahole-ver), 126) += --btf_features=distilled_base
> endif
> --
> 2.31.1
>
next prev parent reply other threads:[~2024-07-01 23:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 17:31 [PATCH bpf-next] kbuild, bpf: reproducible BTF from pahole when KBUILD_BUILD_TIMESTAMP set Alan Maguire
2024-07-01 23:07 ` Jiri Olsa [this message]
2024-07-02 7:58 ` Masahiro Yamada
2024-07-02 8:20 ` asmadeus
2024-07-02 9:49 ` Alan Maguire
2024-07-15 11:19 ` Masahiro Yamada
2024-07-20 12:12 ` asmadeus
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=ZoM2tY2QdD-41g80@krava \
--to=olsajiri@gmail.com \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=asmadeus@codewreck.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=linux-kbuild@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=nicolas@fjasle.eu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox