From: Julia Lawall <julia.lawall@inria.fr>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org,
Masahiro Yamada <masahiroy@kernel.org>,
Michal Marek <michal.lkml@markovi.net>,
linux-kbuild@vger.kernel.org
Subject: Re: build reproducibility
Date: Sun, 17 Oct 2021 20:42:31 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2110172041010.4761@hadrien> (raw)
In-Reply-To: <7e5485df-a17b-304b-627d-9a85d2464df3@infradead.org>
On Sun, 17 Oct 2021, Randy Dunlap wrote:
> On 10/17/21 11:12 AM, Julia Lawall wrote:
> > Hello,
> >
> > If I do the following:
> >
> > git clean -dfx
> > cp saved_config .config
> > make olddefconfig && make && make modules_install && make install
> >
> > Should I always end up with the same kernel, regardless of the kernel that
> > is currently running on the machine?
> >
> > I see a large performance difference between Linux 5.10 and all versions
> > afterwards for a particular benchmark. I am unable to bisect the problem
> > eg between 5.10 and 5.11, because as soon as I come to a kernel that gives
> > the bad performance, all of the kernels that I generate subsequently in
> > the bisecting process (using the above commands) also have the bad
> > performance.
> >
> > It could of course be that I have completely misinterpreted the problem,
> > and it has nothing to do with the kernel. But I have tested the program a
> > lot when only working on variants of Linux 5.9. I only start to have
> > problems when I use versions >= 5.11.
>
> Hi,
>
> My "guess" is that this has something to do with the build
> reusing some current file(s) that need to be rebuilt.
> I.e., adding a "make clean" or "make proper" might be needed.
This was my guess too. But I have the git clean -dfx. I did a comparison
with make distclean and this does a little more (mostly some files in
tools).
thanks,
julia
>
> I say this only because sometimes I cannot even reproduce
> a build that has errors or warnings unless I prefix it with
> make clean or mrproper. (i.e., nothing to do with booting
> and running the new kernel)
> Even though the .config file has changed and I do
> "make olddefconfig", the same build errors do not show up
> unless I do the clean or mrproper step also.
>
>
> --
> ~Randy
>
next prev parent reply other threads:[~2021-10-17 18:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-17 18:12 build reproducibility Julia Lawall
2021-10-17 18:32 ` Randy Dunlap
2021-10-17 18:42 ` Julia Lawall [this message]
2021-10-18 2:26 ` Masahiro Yamada
2021-10-18 2:40 ` Willy Tarreau
2021-10-18 5:51 ` Julia Lawall
2021-10-18 5:59 ` Willy Tarreau
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=alpine.DEB.2.22.394.2110172041010.4761@hadrien \
--to=julia.lawall@inria.fr \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=rdunlap@infradead.org \
/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