From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (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 DA68C3F4DC0 for ; Wed, 20 May 2026 18:09:05 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779300546; cv=none; b=X1MCZ4eC77j1XRQ4NuNsnWtHE+icQJpdS0xweKJtADnbiMcNSssyIpnuO9yABemsAUxTGXz5APKzeKcu/X389M9Rn7MpUaBz848Wtk0H2VqImSoDB0mSxZauPDQMx9jC9GpTsHaXlvZsdMwDknZhKzCD4MktWSxe3cFndeNcrrM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779300546; c=relaxed/simple; bh=ZMldX69DmN7pv+i5GEFyvI9rcNCJz/bryDjkuY2FenU=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=LzRULwQhFAl7Mav9AB4szekHaA+ZKzXu/Iw9EYsCmqLbf6bZtgTjNXOzSnzmZDMvHNH8eAeQFUi8d/7mpgyJA3Gs8Ik59LE6exF609HlKM6mAY5EKvJaotNLg5MsvwAI9d4f89rUmtUYp1uveNlnfK9oXPTvSigyNDCL9ujM06g= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=oqlSd3sP; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="oqlSd3sP" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 732CA1F000E9; Wed, 20 May 2026 18:09:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1779300545; bh=R56s3B2wg1WcZt7b4lQjJ7vwdwBHHXieqoF0JG9TiRk=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=oqlSd3sPppR2UzkuIERs7Ccn6W5Kth5Fyz8y/fc9r/TGmfR2uPyvkuw5zFvVXwIjN 9dxF42VSYdEmyrqMK1F2+inAmfPu2CQ+bJgv4iHs+rpAuAYoO0YHNhb9HDkXzL27Q8 o7oacthv6yhuu7Hl72kv3msH7XYLnqF1rfDSTfTWAaofqEc9YO0kDfOe9a70XTiw4V QkDiUnuI8D+2FTWCe3nyvb4W+EGaiNTNi1MWbeCJxvMvg+YrZyxQFDsXHNn7tZUZCg 65nO8oNOTEzp3ApxEPA+nkat5+hhJcTCquhdV7/eXhH8g0jUflmheft59Z4enmMkQw mmqafJNC8CiEg== Date: Wed, 20 May 2026 08:09:04 -1000 From: Tejun Heo To: Shrikanth Hegde Cc: Steven Rostedt , Valentin Schneider , LKML , Peter Zijlstra , Juri Lelli , Vincent Guittot , Dietmar Eggemann , Ben Segall , Mel Gorman , K Prateek Nayak , Kyle McMartin Subject: Re: [PATCH v2] sched/rt: Have RT_PUSH_IPI be default off for non PREEMPT_RT Message-ID: References: <20260515103740.25ccbed8@gandalf.local.home> <61203cdb-af98-47e6-bb70-78af7f0f1cbc@linux.ibm.com> <20260520125226.50b83e76@gandalf.local.home> <310c1f04-562e-4e81-9d39-0f28e1cc414c@linux.ibm.com> Precedence: bulk X-Mailing-List: linux-kernel@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: <310c1f04-562e-4e81-9d39-0f28e1cc414c@linux.ibm.com> On Wed, May 20, 2026 at 10:34:35PM +0530, Shrikanth Hegde wrote: > By any chance it is running with preempt=none/voluntary? > If so it might never call schedule until it goes back to user space. I think this might be it. In the production dump, the locked up cpus were often running btrfs compression / decompression. The kernel is PREEMPT_NONE and while that path has resched_curr()'s, with high enough irq frequency, it wouldn't be that difficult to catch the cpu enough times before it reaches the resched point. Thanks. -- tejun