From nobody Sat Oct 4 05:02:44 2025 Received: from mail-oa1-f73.google.com (mail-oa1-f73.google.com [209.85.160.73]) (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 6180132A3FA for ; Wed, 20 Aug 2025 16:22:50 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.160.73 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1755706972; cv=none; b=BbmG6G2i0ErrjiMP8sKaVDIg+hrCouxm3G/AqwX9ZTzdiocPaVmfvfx00gSzkIQbQqVuXPnG2pYioodts3c35T21d16t3/SV91YrsfUwmkKgF+QJb9YDSVyyFCLqiOQ5S+v4bVIlZ74Tquz/VoQ4LQGCFY04UmeX9iZdy4S2ETI= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1755706972; c=relaxed/simple; bh=6Ji2BMWpHylbG3Gk41TqRwy1xuilBvKN/0gbdpGP9KY=; h=Date:In-Reply-To:Mime-Version:References:Message-ID:Subject:From: To:Cc:Content-Type; b=OcoqgTseIRUsuKkam0y4G1z+3BGL0yYPb3tXvJLBMFEI8HnV8Do+2DTqSDjBal1bn9SbYw/Rv1LsHyAz3quIW8wfKGCWs4e3aKPv+m6Kc5oLcezk9qNaTUtI6P9J9yk5u3ujb2uvqCyLhqF9XJd6UNVHl9LMo6xfZL27tWj+MLU= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=google.com; spf=pass smtp.mailfrom=flex--rananta.bounces.google.com; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b=T9DN/prH; arc=none smtp.client-ip=209.85.160.73 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=google.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=flex--rananta.bounces.google.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b="T9DN/prH" Received: by mail-oa1-f73.google.com with SMTP id 586e51a60fabf-30ccebfdef3so231498fac.2 for ; Wed, 20 Aug 2025 09:22:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20230601; t=1755706969; x=1756311769; darn=vger.kernel.org; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:from:to:cc:subject:date:message-id:reply-to; bh=IxgL3AzDrrZHKcYrme0egJ79bqapQGokq5EDgAEIJ+c=; b=T9DN/prHCLRHDKEg8HNNUt5PXib2NHcFO5nuYAS48jZL4LMciGW3c90pbf+MZI+ttj HhbTLDsLQOgJTzHaGhhe8GyG35leLdWAvIBKIJOU+rWqHw6HO0z5/KnwgPC6ZMWuU21i jmqbaQufBFABvHHC2xvBWbXEU9Fn1SLyqZLUn7o4QV00P7FMrH0U/QE7yFZWGdtZ5Rmg a9jgLOPtoEITUMCT4SY391fVggOjT93x8wn713HSKObwW2eaGo02ZYUmpPTfzBGwI8FG ZHHEFzoIv+E064Fxj+Ig2EcToTcJSd2We+9iDcBae7cIoWjJuDbNGaf40yCdPuYhnrqC 5o/w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1755706969; x=1756311769; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=IxgL3AzDrrZHKcYrme0egJ79bqapQGokq5EDgAEIJ+c=; b=wW1HphcKYdJgyybxhqIo7sD7vtzYPcCJKE/xNViUenKUdsxk4OzuLCcwONh3X8lkZR iydFcSF16aVczw8EogAyVPwyQ4XqCwZX6kCcrXf5s3yn9uHYsILq1i5fT4gvgbrl6R6l NX+Gqw4fZFr+tXCBnOmuGOwjarXfnqdeSmQe7qDdfgN7jvpTbn+QvOGtRYIycZy807k/ AwGAxpoTVHetTUPqM+25SozZ5DIhYS6m2mIPzBuI1jf0k+/VR17NlOH+jralM7QEFqV+ UIbgPe3VJKTtf7wrkA7M5WHTEh7gO8zId3krcCUYO+GCHxEfr9Lp80EKi7uQHcVok0E7 tWNA== X-Forwarded-Encrypted: i=1; AJvYcCWvpYP4Gob6fOJ1CX2yykx0uwDzy1P5+xi6lFptusLU8McWqT3Prp4RepFJeM7zsFVctyzsLvQKgscwv7U=@vger.kernel.org X-Gm-Message-State: AOJu0Yx2rrEfhw+ar9IYOVlIAKTvwuNZ7tmUGwViwC6CHkc9EhOpb+eM ougSTVH3UeqfE0e6L6qB4RqQGknhsiCZaDliqnear0DUHCN346rMZ1We302Uq4KcAsUNkgzfFAQ 41M+3psljNA== X-Google-Smtp-Source: AGHT+IGHN40LChKmW4U+xn4mYc2JbS9gSROkMCaEkVyOWl8ZTwAYUdz9gBc8qFeauFM0HFD3Zo+x0vJsjUGN X-Received: from oabxe23.prod.google.com ([2002:a05:6870:ce97:b0:29d:f69c:1743]) (user=rananta job=prod-delivery.src-stubby-dispatcher) by 2002:a05:687c:2be8:b0:306:9f1d:da2a with SMTP id 586e51a60fabf-31122769fd5mr2072917fac.5.1755706969532; Wed, 20 Aug 2025 09:22:49 -0700 (PDT) Date: Wed, 20 Aug 2025 16:22:42 +0000 In-Reply-To: <20250820162242.2624752-1-rananta@google.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 References: <20250820162242.2624752-1-rananta@google.com> X-Mailer: git-send-email 2.51.0.rc2.233.g662b1ed5c5-goog Message-ID: <20250820162242.2624752-3-rananta@google.com> Subject: [PATCH v2 2/2] KVM: arm64: Reschedule as needed when destroying the stage-2 page-tables From: Raghavendra Rao Ananta To: Oliver Upton , Marc Zyngier Cc: Raghavendra Rao Anata , Mingwei Zhang , linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev, linux-kernel@vger.kernel.org, kvm@vger.kernel.org Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" When a large VM, specifically one that holds a significant number of PTEs, gets abruptly destroyed, the following warning is seen during the page-table walk: sched: CPU 0 need_resched set for > 100018840 ns (100 ticks) without sched= ule CPU: 0 UID: 0 PID: 9617 Comm: kvm_page_table_ Tainted: G O 6.16.0-smp-DEV = #3 NONE Tainted: [O]=3DOOT_MODULE Call trace: show_stack+0x20/0x38 (C) dump_stack_lvl+0x3c/0xb8 dump_stack+0x18/0x30 resched_latency_warn+0x7c/0x88 sched_tick+0x1c4/0x268 update_process_times+0xa8/0xd8 tick_nohz_handler+0xc8/0x168 __hrtimer_run_queues+0x11c/0x338 hrtimer_interrupt+0x104/0x308 arch_timer_handler_phys+0x40/0x58 handle_percpu_devid_irq+0x8c/0x1b0 generic_handle_domain_irq+0x48/0x78 gic_handle_irq+0x1b8/0x408 call_on_irq_stack+0x24/0x30 do_interrupt_handler+0x54/0x78 el1_interrupt+0x44/0x88 el1h_64_irq_handler+0x18/0x28 el1h_64_irq+0x84/0x88 stage2_free_walker+0x30/0xa0 (P) __kvm_pgtable_walk+0x11c/0x258 __kvm_pgtable_walk+0x180/0x258 __kvm_pgtable_walk+0x180/0x258 __kvm_pgtable_walk+0x180/0x258 kvm_pgtable_walk+0xc4/0x140 kvm_pgtable_stage2_destroy+0x5c/0xf0 kvm_free_stage2_pgd+0x6c/0xe8 kvm_uninit_stage2_mmu+0x24/0x48 kvm_arch_flush_shadow_all+0x80/0xa0 kvm_mmu_notifier_release+0x38/0x78 __mmu_notifier_release+0x15c/0x250 exit_mmap+0x68/0x400 __mmput+0x38/0x1c8 mmput+0x30/0x68 exit_mm+0xd4/0x198 do_exit+0x1a4/0xb00 do_group_exit+0x8c/0x120 get_signal+0x6d4/0x778 do_signal+0x90/0x718 do_notify_resume+0x70/0x170 el0_svc+0x74/0xd8 el0t_64_sync_handler+0x60/0xc8 el0t_64_sync+0x1b0/0x1b8 The warning is seen majorly on the host kernels that are configured not to force-preempt, such as CONFIG_PREEMPT_NONE=3Dy. To avoid this, instead of walking the entire page-table in one go, split it into smaller ranges, by checking for cond_resched() between each range. Since the path is executed during VM destruction, after the page-table structure is unlinked from the KVM MMU, relying on cond_resched_rwlock_write() isn't necessary. Signed-off-by: Raghavendra Rao Ananta Suggested-by: Oliver Upton --- arch/arm64/kvm/mmu.c | 26 +++++++++++++++++++++++++- 1 file changed, 25 insertions(+), 1 deletion(-) diff --git a/arch/arm64/kvm/mmu.c b/arch/arm64/kvm/mmu.c index e41fc7bcee24..0d6d42a86126 100644 --- a/arch/arm64/kvm/mmu.c +++ b/arch/arm64/kvm/mmu.c @@ -903,11 +903,35 @@ static int kvm_init_ipa_range(struct kvm_s2_mmu *mmu,= unsigned long type) return 0; } =20 +/* + * Assume that @pgt is valid and unlinked from the KVM MMU to free the + * page-table without taking the kvm_mmu_lock and without performing any + * TLB invalidations. + * + * Also, the range of addresses can be large enough to cause need_resched + * warnings, for instance on CONFIG_PREEMPT_NONE kernels. Hence, invoke + * cond_resched() periodically to prevent hogging the CPU for a long time + * and schedule something else, if required. + */ +static void stage2_destroy_range(struct kvm_pgtable *pgt, phys_addr_t addr, + phys_addr_t end) +{ + u64 next; + + do { + next =3D stage2_range_addr_end(addr, end); + KVM_PGT_FN(kvm_pgtable_stage2_destroy_range)(pgt, addr, + next - addr); + if (next !=3D end) + cond_resched(); + } while (addr =3D next, addr !=3D end); +} + static void kvm_stage2_destroy(struct kvm_pgtable *pgt) { unsigned int ia_bits =3D VTCR_EL2_IPA(pgt->mmu->vtcr); =20 - KVM_PGT_FN(kvm_pgtable_stage2_destroy_range)(pgt, 0, BIT(ia_bits)); + stage2_destroy_range(pgt, 0, BIT(ia_bits)); KVM_PGT_FN(kvm_pgtable_stage2_destroy_pgd)(pgt); } =20 --=20 2.51.0.rc2.233.g662b1ed5c5-goog