[05/22] KVM: selftests: Enable mmu_stress_test on arm64

Message ID	20240809194335.1726916-6-seanjc@google.com (mailing list archive)
State	New, archived
Headers	show Received: from mail-pl1-f202.google.com (mail-pl1-f202.google.com [209.85.214.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 8610A16D4F5 for <kvm@vger.kernel.org>; Fri, 9 Aug 2024 19:43:49 +0000 (UTC) Reply-To: Sean Christopherson <seanjc@google.com> Date: Fri, 9 Aug 2024 12:43:17 -0700 In-Reply-To: <20240809194335.1726916-1-seanjc@google.com> Precedence: bulk Mime-Version: 1.0 References: <20240809194335.1726916-1-seanjc@google.com> Message-ID: <20240809194335.1726916-6-seanjc@google.com> Subject: [PATCH 05/22] KVM: selftests: Enable mmu_stress_test on arm64 From: Sean Christopherson <seanjc@google.com> To: Sean Christopherson <seanjc@google.com>, Paolo Bonzini <pbonzini@redhat.com> Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Oliver Upton <oliver.upton@linux.dev>, Marc Zyngier <maz@kernel.org>, Peter Xu <peterx@redhat.com>, James Houghton <jthoughton@google.com> Content-Type: text/plain; charset="UTF-8"
Series	KVM: x86/mmu: Allow yielding on mmu_notifier zap \| expand [00/22] KVM: x86/mmu: Allow yielding on mmu_notifier zap [01/22] KVM: selftests: Check for a potential unhandled exception iff KVM_RUN succeeded [02/22] KVM: selftests: Rename max_guest_memory_test to mmu_stress_test [03/22] KVM: selftests: Only muck with SREGS on x86 in mmu_stress_test [04/22] KVM: selftests: Compute number of extra pages needed in mmu_stress_test [05/22] KVM: selftests: Enable mmu_stress_test on arm64 [06/22] KVM: selftests: Use vcpu_arch_put_guest() in mmu_stress_test [07/22] KVM: selftests: Precisely limit the number of guest loops in mmu_stress_test [08/22] KVM: selftests: Add a read-only mprotect() phase to mmu_stress_test [09/22] KVM: selftests: Verify KVM correctly handles mprotect(PROT_READ) [10/22] KVM: x86/mmu: Move walk_slot_rmaps() up near for_each_slot_rmap_range() [11/22] KVM: x86/mmu: Plumb a @can_yield parameter into __walk_slot_rmaps() [12/22] KVM: x86/mmu: Add a helper to walk and zap rmaps for a memslot [13/22] KVM: x86/mmu: Honor NEED_RESCHED when zapping rmaps and blocking is allowed [14/22] KVM: x86/mmu: Morph kvm_handle_gfn_range() into an aging specific helper [15/22] KVM: x86/mmu: Fold mmu_spte_age() into kvm_rmap_age_gfn_range() [16/22] KVM: x86/mmu: Add KVM_RMAP_MANY to replace open coded '1' and '1ul' literals [17/22] KVM: x86/mmu: Refactor low level rmap helpers to prep for walking w/o mmu_lock [18/22] KVM: x86/mmu: Use KVM_PAGES_PER_HPAGE() instead of an open coded equivalent [19/22] KVM: x86/mmu: Add infrastructure to allow walking rmaps outside of mmu_lock [20/22] KVM: x86/mmu: Add support for lockless walks of rmap SPTEs [21/22] KVM: x86/mmu: Support rmap walks without holding mmu_lock when aging gfns [22/22] *HACK* KVM: x86: Don't take mmu_lock when aging gfns

Message ID

20240809194335.1726916-6-seanjc@google.com (mailing list archive)

State

New, archived

Headers

Reply-To: Sean Christopherson <seanjc@google.com>
Date: Fri,  9 Aug 2024 12:43:17 -0700
In-Reply-To: <20240809194335.1726916-1-seanjc@google.com>
Precedence: bulk
Mime-Version: 1.0
References: <20240809194335.1726916-1-seanjc@google.com>
Message-ID: <20240809194335.1726916-6-seanjc@google.com>
Subject: [PATCH 05/22] KVM: selftests: Enable mmu_stress_test on arm64
From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
 Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Oliver Upton <oliver.upton@linux.dev>, Marc Zyngier <maz@kernel.org>,
 Peter Xu <peterx@redhat.com>,
	James Houghton <jthoughton@google.com>
Content-Type: text/plain; charset="UTF-8"

Series

KVM: x86/mmu: Allow yielding on mmu_notifier zap | expand

Commit Message

Sean Christopherson Aug. 9, 2024, 7:43 p.m. UTC

Enable the mmu_stress_test on arm64.  The intent was to enable the test
across all architectures when it was first added, but a few goofs made it
unrunnable on !x86.  Now that those goofs are fixed, at least for arm64,
enable the test.

Cc: Oliver Upton <oliver.upton@linux.dev>
Cc: Marc Zyngier <maz@kernel.org>
Signed-off-by: Sean Christopherson <seanjc@google.com>
---
 tools/testing/selftests/kvm/Makefile | 1 +
 1 file changed, 1 insertion(+)

diff --git a/tools/testing/selftests/kvm/Makefile b/tools/testing/selftests/kvm/Makefile
index cc25f19b62da..4198df29503f 100644
--- a/tools/testing/selftests/kvm/Makefile
+++ b/tools/testing/selftests/kvm/Makefile
@@ -174,6 +174,7 @@  TEST_GEN_PROGS_aarch64 += kvm_create_max_vcpus
 TEST_GEN_PROGS_aarch64 += kvm_page_table_test
 TEST_GEN_PROGS_aarch64 += memslot_modification_stress_test
 TEST_GEN_PROGS_aarch64 += memslot_perf_test
+TEST_GEN_PROGS_aarch64 += mmu_stress_test
 TEST_GEN_PROGS_aarch64 += rseq_test
 TEST_GEN_PROGS_aarch64 += set_memory_region_test
 TEST_GEN_PROGS_aarch64 += steal_time

[05/22] KVM: selftests: Enable mmu_stress_test on arm64

Commit Message

Patch