Re: [PATCH v3 5/6] KVM: s390: selftests: enable some common memory-related tests

[Steffen Eiden <seiden@linux.ibm.com>]

On Tue, Apr 07, 2026 at 03:04:38PM +0200, Claudio Imbrenda wrote:
> On Tue, 7 Apr 2026 14:47:52 +0200
> Steffen Eiden <seiden@linux.ibm.com> wrote:
> 
> > 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
> 
> [...]
> 
> > >  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.
> 
> no, loongarch does *not* include TEST_GEN_PROGS_COMMON, so if I
> remove them, they're gone

Ok, my bad. I just did a quick grep for the test names to look for missing
removals. I missed that little detail.

> 
> > 
> > 	Steffen
>