[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wiEf7irTKwPJ0jTMOF3CS-13UXmF6Fns3wuWpOZ_wGyZQ@mail.gmail.com>
Date: Fri, 24 Feb 2023 15:22:58 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Shuah Khan <skhan@...uxfoundation.org>
Cc: shuah <shuah@...nel.org>, David Gow <davidgow@...gle.com>,
Brendan Higgins <brendanhiggins@...gle.com>,
linux-kselftest@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] KUnit next update for Linux 6.3-rc1
On Tue, Feb 21, 2023 at 5:51 PM Shuah Khan <skhan@...uxfoundation.org> wrote:
>
> This KUnit update for Linux 6.3-rc1 consists of cleanups, new features,
> and documentation updates:
Hmm. I have not actually bisected this or tried to otherwise figure
out exactly what is wrong, but the kunit code ends up being really
annoying for my build testing.
In particular, if I do
make
repeatedly - ie with no other changes in between - the kunit code ends
up re-building itself for no apparent reason.
Which then causes a re-link and makes it all really slow.
Maybe I'm barking up the wrong tree, but just do
make allmodconfig
and then do two plain "make"s in succession (feel free to add "-jXYZ"
to make it go much faster ;).
The second build - that shouldn't have to re-build anything - still does this:
CALL scripts/checksyscalls.sh
DESCEND objtool
CHK kernel/kheaders_data.tar.xz
CC lib/kunit/hooks.o
AR lib/built-in.a
CC lib/kunit/hooks.o
AR lib/kunit/lib.a
AR built-in.a
AR vmlinux.a
LD vmlinux.o
...
and it all takes much longer than an empty kernel build _should_ take.
Linus
Powered by blists - more mailing lists