From: Steffen Eiden <seiden@linux.ibm.com>
To: Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
linux-s390@vger.kernel.org, borntraeger@de.ibm.com,
frankja@linux.ibm.com, nrb@linux.ibm.com,
schlameuss@linux.ibm.com, gra@linux.ibm.com, david@kernel.org
Subject: Re: [PATCH v3 5/6] KVM: s390: selftests: enable some common memory-related tests
Date: Tue, 7 Apr 2026 14:47:52 +0200 [thread overview]
Message-ID: <20260407124752.296205-E-seiden@linux.ibm.com> (raw)
In-Reply-To: <20260402150135.196943-6-imbrenda@linux.ibm.com>
On Thu, Apr 02, 2026 at 05:01:34PM +0200, Claudio Imbrenda wrote:
> Enable the following tests on s390:
> * memslot_modification_stress_test
> * memslot_perf_test
> * mmu_stress_test
>
> Since the first two tests are now supported on all architectures, move
> them into TEST_GEN_PROGS_COMMON and out of the indiviual architectures.
>
> Signed-off-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
> ---
> tools/testing/selftests/kvm/Makefile.kvm | 9 +++------
> 1 file changed, 3 insertions(+), 6 deletions(-)
>
> diff --git a/tools/testing/selftests/kvm/Makefile.kvm b/tools/testing/selftests/kvm/Makefile.kvm
> index fdec90e85467..057f17d6b896 100644
> --- a/tools/testing/selftests/kvm/Makefile.kvm
> +++ b/tools/testing/selftests/kvm/Makefile.kvm
> @@ -64,6 +64,8 @@ TEST_GEN_PROGS_COMMON += kvm_binary_stats_test
> TEST_GEN_PROGS_COMMON += kvm_create_max_vcpus
> TEST_GEN_PROGS_COMMON += kvm_page_table_test
> TEST_GEN_PROGS_COMMON += set_memory_region_test
> +TEST_GEN_PROGS_COMMON += memslot_modification_stress_test
> +TEST_GEN_PROGS_COMMON += memslot_perf_test
>
> # Compiled test targets
> TEST_GEN_PROGS_x86 = $(TEST_GEN_PROGS_COMMON)
> @@ -147,8 +149,6 @@ TEST_GEN_PROGS_x86 += coalesced_io_test
> TEST_GEN_PROGS_x86 += dirty_log_perf_test
> TEST_GEN_PROGS_x86 += guest_memfd_test
> TEST_GEN_PROGS_x86 += hardware_disable_test
> -TEST_GEN_PROGS_x86 += memslot_modification_stress_test
> -TEST_GEN_PROGS_x86 += memslot_perf_test
> TEST_GEN_PROGS_x86 += mmu_stress_test
> TEST_GEN_PROGS_x86 += rseq_test
> TEST_GEN_PROGS_x86 += steal_time
> @@ -186,8 +186,6 @@ TEST_GEN_PROGS_arm64 += coalesced_io_test
> TEST_GEN_PROGS_arm64 += dirty_log_memslot_perf_testperf_test
> TEST_GEN_PROGS_arm64 += get-reg-list
> TEST_GEN_PROGS_arm64 += guest_memfd_test
> -TEST_GEN_PROGS_arm64 += memslot_modification_stress_test
> -TEST_GEN_PROGS_arm64 += memslot_perf_test
> TEST_GEN_PROGS_arm64 += mmu_stress_test
> TEST_GEN_PROGS_arm64 += rseq_test
> TEST_GEN_PROGS_arm64 += steal_time
> @@ -205,6 +203,7 @@ TEST_GEN_PROGS_s390 += s390/ucontrol_test
> TEST_GEN_PROGS_s390 += s390/user_operexec
> TEST_GEN_PROGS_s390 += s390/keyop
> TEST_GEN_PROGS_s390 += rseq_test
> +TEST_GEN_PROGS_s390 += mmu_stress_test
>
> TEST_GEN_PROGS_riscv = $(TEST_GEN_PROGS_COMMON)
> TEST_GEN_PROGS_riscv += riscv/sbi_pmu_test
> @@ -214,8 +213,6 @@ TEST_GEN_PROGS_riscv += arch_timer
> TEST_GEN_PROGS_riscv += coalesced_io_test
> TEST_GEN_PROGS_riscv += dirty_log_perf_test
> TEST_GEN_PROGS_riscv += get-reg-list
> -TEST_GEN_PROGS_riscv += memslot_modification_stress_test
> -TEST_GEN_PROGS_riscv += memslot_perf_test
> TEST_GEN_PROGS_riscv += mmu_stress_test
> TEST_GEN_PROGS_riscv += rseq_test
> TEST_GEN_PROGS_riscv += steal_time
> --
I think you missed removing the loongarch targets.
Steffen
next prev parent reply other threads:[~2026-04-07 12:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 15:01 [PATCH v3 0/6] KVM: s390: Enable 4k granularity for memslots Claudio Imbrenda
2026-04-02 15:01 ` [PATCH v3 1/6] KVM: s390: Add some useful mask macros Claudio Imbrenda
2026-04-07 12:13 ` Steffen Eiden
2026-04-02 15:01 ` [PATCH v3 2/6] KVM: s390: Add alignment checks for hugepages Claudio Imbrenda
2026-04-07 12:30 ` Steffen Eiden
2026-04-02 15:01 ` [PATCH v3 3/6] KVM: s390: Allow 4k granularity for memslots Claudio Imbrenda
2026-04-07 12:33 ` Steffen Eiden
2026-04-02 15:01 ` [PATCH v3 4/6] KVM: selftests: Remove 1M alignment requirement for s390 Claudio Imbrenda
2026-04-07 12:44 ` Steffen Eiden
2026-04-02 15:01 ` [PATCH v3 5/6] KVM: s390: selftests: enable some common memory-related tests Claudio Imbrenda
2026-04-07 12:47 ` Steffen Eiden [this message]
2026-04-07 13:04 ` Claudio Imbrenda
2026-04-07 13:41 ` Steffen Eiden
2026-04-07 15:19 ` Steffen Eiden
2026-04-02 15:01 ` [PATCH v3 6/6] KVM: s390: ucontrol: Fix memslot handling Claudio Imbrenda
2026-04-07 12:55 ` Steffen Eiden
2026-04-07 13:05 ` Claudio Imbrenda
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=20260407124752.296205-E-seiden@linux.ibm.com \
--to=seiden@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=david@kernel.org \
--cc=frankja@linux.ibm.com \
--cc=gra@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nrb@linux.ibm.com \
--cc=schlameuss@linux.ibm.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