From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-178.mta0.migadu.com (out-178.mta0.migadu.com [91.218.175.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 4499624A1D for ; Tue, 5 Mar 2024 19:49:47 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.178 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1709668189; cv=none; b=jt1ya39AHRN2i/LDpESLJsjf+40WniZerJfH8C3p5s3b2cZWHwtYvZlpIPg0WmYp9Rt2Cf5L7efSqu0D+RUqButKDgWoq6fqV3335dYYGdx/ccK+Dfj5jP3tDlJLOWHSH8x9w8TuLXk8YSyAvhatGBTAZkFoHxVitGSlJ9SxJVs= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1709668189; c=relaxed/simple; bh=+WKDowJ/Vyo6jEXEBn5BtLH+g7pYLXM9AnPMMTv2bzY=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=MFniZB+fhtKovTGWrrpZaT67qubc0U3uxiEOPurVBisQ3irA3mxrqN0NSLXDm88pb3EnKjkmSFZPg0sB18xjEmSO1ts8iHhyA/s64qKj8lt43bGD0sksfHNJkeYWoTHexOYchW4CFjJQl3jOAaJEvowS7W1xGgBdaKfgrUQ/srk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=WqPxyIUv; arc=none smtp.client-ip=91.218.175.178 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="WqPxyIUv" Date: Tue, 5 Mar 2024 19:49:35 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1709668185; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Z6IK7WTxYDII1ZZxniDW+JY/tgmWm66Vu1jWnH6jiRw=; b=WqPxyIUvJbTV79UAzinYrjAvZXcW8HGl7VrNMOVbVNT/0O7k1Ewhrkj5Ft8HkntmqFn9WS JHT1SKWyIbrYqUns5W/KZ59IJHyxbMfCHyIhGc9v8olorlZhcdLkBtlGGf0oPRs4YkEdtf MNPL9vXFLouuU/C4RYbgpz6yz2+9KEc= X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Oliver Upton To: Krister Johansen Cc: stable@vger.kernel.org, Marc Zyngier , James Morse , Alexandru Elisei , David Matlack , kvm@vger.kernel.org Subject: Re: [PATCH 5.15.y 0/2] fix softlockups in stage2_apply_range() Message-ID: References: Precedence: bulk X-Mailing-List: stable@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Migadu-Flow: FLOW_OUT On Tue, Mar 05, 2024 at 11:41:38AM -0800, Krister Johansen wrote: > Hi Stable Team, > In 5.15, unmapping large kvm vms on arm64 can generate softlockups. My team has > been hitting this when tearing down VMs > 100Gb in size. > > Oliver fixed this with the attached patches. They've been in mainline since > 6.1. > > I tested on 5.15.150 with these patches applied. When they're present, > both the dirty_log_perf_test detailed in the second patch, and > kvm_page_table_test no longer generate softlockups when unmapping VMs > with large memory configurations. > > Would you please consider these patches for inclusion in an upcoming 5.15 > release? Backport looks fine, and I have no issues with this going to stable if it helps folks. Acked-by: Oliver Upton -- Thanks, Oliver