linux-kselftest.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: shuah <shuah@kernel.org>, David Gow <davidgow@google.com>,
	Brendan Higgins <brendanhiggins@google.com>,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] KUnit next update for Linux 6.3-rc1
Date: Fri, 24 Feb 2023 15:22:58 -0800	[thread overview]
Message-ID: <CAHk-=wiEf7irTKwPJ0jTMOF3CS-13UXmF6Fns3wuWpOZ_wGyZQ@mail.gmail.com> (raw)
In-Reply-To: <02cf36b9-6526-576b-1fd3-a59b67c8c123@linuxfoundation.org>

On Tue, Feb 21, 2023 at 5:51 PM Shuah Khan <skhan@linuxfoundation.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

  parent reply	other threads:[~2023-02-24 23:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-22  1:50 [GIT PULL] KUnit next update for Linux 6.3-rc1 Shuah Khan
2023-02-23 18:47 ` pr-tracker-bot
2023-02-24 23:22 ` Linus Torvalds [this message]
2023-02-25  0:25   ` David Gow
2023-02-25  1:50     ` David Gow

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='CAHk-=wiEf7irTKwPJ0jTMOF3CS-13UXmF6Fns3wuWpOZ_wGyZQ@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=brendanhiggins@google.com \
    --cc=davidgow@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=skhan@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).