From: Sasha Levin <sashal@kernel.org>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: Shuah Khan <shuah@kernel.org>,
kvm@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] KVM: selftests: add empty install and run_tests targets for unsupported ARCHs
Date: Wed, 4 Nov 2026 14:36:35 -0500 [thread overview]
Message-ID: <20261104193635.333141-1-sashal@kernel.org> (raw)
Commit 43fbd8cd389f ("KVM: selftests: Provide empty 'all' and 'clean'
targets for unsupported ARCHs") gave the KVM selftests empty all and
clean targets on architectures without KVM selftests, such as 32-bit
arm and i386. The selftests Makefile also runs install and run_tests
in each suite, and those still fail there:
make[1]: *** No rule to make target 'install'. Stop.
Add empty install and run_tests targets as well.
Fixes: 43fbd8cd389f ("KVM: selftests: Provide empty 'all' and 'clean' targets for unsupported ARCHs")
Signed-off-by: Sasha Levin <sashal@kernel.org>
---
Found with KernelCI-style TuxMake builds that record per-suite results
with KSFT_BUILD_REPORT. 32-bit arm builds now succeed without installing
anything.
tools/testing/selftests/kvm/Makefile | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tools/testing/selftests/kvm/Makefile b/tools/testing/selftests/kvm/Makefile
index 03d91f00092f4..3881df8d5b2b8 100644
--- a/tools/testing/selftests/kvm/Makefile
+++ b/tools/testing/selftests/kvm/Makefile
@@ -13,4 +13,6 @@ else
# Empty targets for unsupported architectures
all:
clean:
+install:
+run_tests:
endif
--
2.53.0
next reply other threads:[~2026-11-04 19:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 19:36 Sasha Levin [this message]
2026-11-04 23:02 ` Sean Christopherson
2026-11-04 23:38 ` Sasha Levin
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=20261104193635.333141-1-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=shuah@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
all inboxes | Powered by JetHome®