From: Andrew Morton <akpm@linux-foundation.org>
To: Li Wang <liwang@redhat.com>
Cc: linux-kbuild@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: tools/testing/selftests
Date: Fri, 27 Mar 2026 21:09:29 -0700 [thread overview]
Message-ID: <20260327210929.f3a714186aed347f90f71246@linux-foundation.org> (raw)
In-Reply-To: <acc49s7jbI9Q3a4f@redhat.com>
On Sat, 28 Mar 2026 10:12:06 +0800 Li Wang <liwang@redhat.com> wrote:
> On Fri, Mar 27, 2026 at 02:32:34PM -0700, Andrew Morton wrote:
> >
> > whinges, perrmanits, maybe I'm doing it wrong, etc.
> >
> > a)
> >
> > At the top-level, neither `make mrproper' nor `make clean' remove the
> > executables from tools/testing/selftests/mm/. Seems wrong?
> >
> > b)
> >
> > Shouldn't I be able to run
> >
> > make selftests
> >
> > from the top level?
>
> Should use:
>
> make kselftest
> make kselftest-clean
Thanks.
> Those two binaries (*_32 / *_64) are built by custom rules in mm/Makefile.
> (Makefile: line #218, #226).
>
> Other tests use shared rules from ../lib.mk, which are quieter (they hide
> full commands and show short CC ... lines).
>
> Maybe we need:
>
> --- a/tools/testing/selftests/mm/Makefile
> +++ b/tools/testing/selftests/mm/Makefile
> @@ -215,7 +215,8 @@ ifeq ($(CAN_BUILD_I386),1)
> $(BINARIES_32): CFLAGS += -m32 -mxsave
> $(BINARIES_32): LDLIBS += -lrt -ldl -lm
> $(BINARIES_32): $(OUTPUT)/%_32: %.c
> - $(CC) $(CFLAGS) $(EXTRA_CFLAGS) $(notdir $^) $(LDLIBS) -o $@
> + $(call msg,CC,,$@)
> + $(Q)$(CC) $(CFLAGS) $(EXTRA_CFLAGS) $(notdir $^) $(LDLIBS) -o $@
> $(foreach t,$(VMTARGETS),$(eval $(call gen-target-rule-32,$(t))))
> endif
>
> @@ -223,7 +224,8 @@ ifeq ($(CAN_BUILD_X86_64),1)
> $(BINARIES_64): CFLAGS += -m64 -mxsave
> $(BINARIES_64): LDLIBS += -lrt -ldl
> $(BINARIES_64): $(OUTPUT)/%_64: %.c
> - $(CC) $(CFLAGS) $(EXTRA_CFLAGS) $(notdir $^) $(LDLIBS) -o $@
> + $(call msg,CC,,$@)
> + $(Q)$(CC) $(CFLAGS) $(EXTRA_CFLAGS) $(notdir $^) $(LDLIBS) -o $@
> $(foreach t,$(VMTARGETS),$(eval $(call gen-target-rule-64,$(t))))
> endif
OK, minor thing of course.
> > d) within tools/testing/selftests/mm:
> >
> > make clean
> > make -j100
> >
> > compiles 3-4 things then ends.
> >
> > A subsequent `make -j1' compiles nothing.
>
> Sorry, I wan't able to reproduce it.
> Did you mean -j100 only build few source file but not the whole?
Yes.
On my 128 core machine everything up to -j50 works. -j51 and higher do
this.
Another (32 core) machine runs -j100 successfully.
Weird.
next prev parent reply other threads:[~2026-03-28 4:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 21:32 tools/testing/selftests Andrew Morton
2026-03-28 2:12 ` tools/testing/selftests Li Wang
2026-03-28 4:09 ` Andrew Morton [this message]
2026-03-29 9:29 ` tools/testing/selftests Li Wang
[not found] ` <20260328135650.435b415f8c00835b2fa471e0@linux-foundation.org>
2026-03-28 21:03 ` tools/testing/selftests Andrew Morton
2026-03-29 10:04 ` tools/testing/selftests Li Wang
2026-03-31 0:09 ` tools/testing/selftests Andrew Morton
2026-03-31 1:52 ` tools/testing/selftests Li Wang
2026-03-31 3:49 ` tools/testing/selftests Andrew Morton
2026-03-31 5:09 ` tools/testing/selftests Li Wang
2026-04-01 0:00 ` tools/testing/selftests Shuah Khan
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=20260327210929.f3a714186aed347f90f71246@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=liwang@redhat.com \
/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