From: Andrew Morton <akpm@linux-foundation.org>
To: linux-kbuild@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: tools/testing/selftests
Date: Fri, 27 Mar 2026 14:32:34 -0700 [thread overview]
Message-ID: <20260327143234.40bb8a0119bd55670ddfeec6@linux-foundation.org> (raw)
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?
c)
tools/testing/selftests/mm
make clean
make
does:
CC droppable
CC guard-regions
CC merge
CC rmap
CC soft-dirty
gcc -Wall -O2 -I /usr/src/25/tools/testing/selftests/../../.. -isystem /usr/src/25/tools/testing/selftests/../../../usr/include -isystem /usr/src/25/tools/testing/selftests/../../../tools/include/uapi -Wunreachable-code -U_FORTIFY_SOURCE -no-pie -D_GNU_SOURCE= -I/usr/src/25/tools/testing/selftests/../../../tools/testing/selftests -m32 -mxsave protection_keys.c vm_util.c thp_settings.c pkey_util.c -lrt -lpthread -lm -lrt -ldl -lm -o /usr/src/25/tools/testing/selftests/mm/protection_keys_32
gcc -Wall -O2 -I /usr/src/25/tools/testing/selftests/../../.. -isystem /usr/src/25/tools/testing/selftests/../../../usr/include -isystem /usr/src/25/tools/testing/selftests/../../../tools/include/uapi -Wunreachable-code -U_FORTIFY_SOURCE -no-pie -D_GNU_SOURCE= -I/usr/src/25/tools/testing/selftests/../../../tools/testing/selftests -m32 -mxsave pkey_sighandler_tests.c vm_util.c thp_settings.c pkey_util.c -lrt -lpthread -lm -lrt -ldl -lm -o /usr/src/25/tools/testing/selftests/mm/pkey_sighandler_tests_32
why did it start emitting the gcc command lines?
d) within tools/testing/selftests/mm:
make clean
make -j100
compiles 3-4 things then ends.
A subsequent `make -j1' compiles nothing.
Whereas
make clean
make -j1
compiles everything. Slowly.
Thanks.
next reply other threads:[~2026-03-27 21:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 21:32 Andrew Morton [this message]
2026-03-28 2:12 ` tools/testing/selftests Li Wang
2026-03-28 4:09 ` tools/testing/selftests Andrew Morton
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=20260327143234.40bb8a0119bd55670ddfeec6@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.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