From: Willy Tarreau <w@1wt.eu>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: Randy Dunlap <rdunlap@infradead.org>,
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: Mon, 18 Oct 2021 07:59:29 +0200 [thread overview]
Message-ID: <20211018055929.GB15718@1wt.eu> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2110180746440.3174@hadrien>
On Mon, Oct 18, 2021 at 07:51:13AM +0200, Julia Lawall wrote:
> My impression is that there is a real
> performance problem in 5.11. The part I don't understand is why once I
> have booted that kernel, all of the kernels I make afterwards have the
> same performance characteristics.
>
> If I do git clean -dfx, then copy a fixed configuration to .config, and
> then use make olddefconfig, should anything about the currently running
> kernel have an impact on the kernel that is produced?
Normally not at all, especially if you restart from a fixed .config. By
the way, you should compare the resulting .config after "make oldconfig"
for all your kernels, in case you spot a difference there, but there is
no reason for that difference to depend on the currently running kernel.
Or maybe it detects something related to your machine and adjusts the
.config accordingly, and that detection depends on the running kernel
(e.g. CPU affecting default optims etc) ? If that's the case you'll see
it in the final .config.
> I'll try simply rebooting the machine on each git bisect step. That
> should eliminate one more aspect of local state.
Just to be avoid wasting your time, perform a cold reboot (reset button).
If you just do a hot reboot and the problem persists, there will still
be a tiny part of doubt leaving a "what if" in your mind that will make
you want to run it all again.
Willy
prev parent reply other threads:[~2021-10-18 5:59 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
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 [this message]
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=20211018055929.GB15718@1wt.eu \
--to=w@1wt.eu \
--cc=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