From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mout-p-202.mailbox.org (mout-p-202.mailbox.org [80.241.56.172]) (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 7EC3A2F25F3 for ; Tue, 11 Aug 2026 07:29:22 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=80.241.56.172 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786433363; cv=none; b=BeyAbrgEkba+3rBYca4im5CxwAl8Mz2gg7Q0yhMRwHhIGx2doJ39ExXaJNhPyoTVD5+AFUVn4XGBrmcoR9ZmZ8lSqSLSw3QqUgAxGj8USOXVcYjEDD0OJdT+rd/tZfqZcwyQcWF2OG/+F/UDvkEcVh++R7i3GfeFfnPRXpKY2TI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786433363; c=relaxed/simple; bh=+4uurmhz/gFAz1ktMFv7oDxYCBjoixUMjupFd8mXcfI=; h=Message-ID:Subject:From:To:Cc:Date:In-Reply-To:References: Content-Type:MIME-Version; b=SUMbZybHc/M5TNzTZrXTLUGCJ/EdsNC2fJzbiYrrqZrSP2hb4mRsRsxeISnn49Ul9PPWt/gmgQTNEI772MyHwAaWMDYokSf37K85WXuMQEVdgAx0K1rXYHnuPTJd1dXorvGOej9lI76FAj3VAxFMyg8rH6MfXRP8qhzGkPMDQQI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=mailbox.org; spf=pass smtp.mailfrom=mailbox.org; dkim=pass (2048-bit key) header.d=mailbox.org header.i=@mailbox.org header.b=OaG5ZbyE; arc=none smtp.client-ip=80.241.56.172 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=mailbox.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=mailbox.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=mailbox.org header.i=@mailbox.org header.b="OaG5ZbyE" Received: from smtp102.mailbox.org (smtp102.mailbox.org [IPv6:2001:67c:2050:b231:465::102]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-p-202.mailbox.org (Postfix) with ESMTPS id 4hK3Cg1SVnzMlLV; Tue, 11 Aug 2026 09:29:19 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mailbox.org; s=mail20150812; t=1786433359; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=+4uurmhz/gFAz1ktMFv7oDxYCBjoixUMjupFd8mXcfI=; b=OaG5ZbyEMmKJ5TslKKTdyPfdrtGU3ej55jlxU9KMdwtTedMKGge4GLt4KkAKziv633cdtd NLVkrV6T7A/93q/+n3NsrgbGgDf/ntD3/P579Qb0j5FnIx+S9rFknCKt4WE7Fl4SuLtoLq nbJOmW7CbF/c3hbLN0P+52quJ2rInCCCQV3JcIYiwr471QV4cvGV5QX1tkgX1iUQYZqz8e eWrfAzU8/09zrVW9mnD1iDfUNUs9Ya7cLSuCmSRbFSUJ9hUAcZP6PBGixJI8dOnvTqeLKX cz8nGfZSirSZeIl8/VtNWWTxqjV3pBz4RT5ZgH1o6ErQUAc7ojN66iKxSROhrQ== Message-ID: Subject: Re: [REGRESSION] drm/sched: FAIR policy causes serious performance degradation at max GPU load on 9070XT From: Philipp Stanner Reply-To: phasta@kernel.org To: Luke.Wildhardt@proton.me, Tvrtko Ursulin Cc: Danilo Krummrich , phasta@kernel.org, "matthew.brost@intel.com" , "ckoenig.leichtzumerken@gmail.com" , "dri-devel@lists.freedesktop.org" , "regressions@lists.linux.dev" , "amd-gfx@lists.freedesktop.org" , "linux-kernel@vger.kernel.org" Date: Tue, 11 Aug 2026 09:29:13 +0200 In-Reply-To: References: <6e2a207e-4db6-4d47-b1f6-9cb13b8d6eeb@igalia.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-MBO-RS-META: qawuyb5ic8ztzk5pkjzpf8tjmyq5dqcg X-MBO-RS-ID: e8842c3fbe0a84fa24a On Mon, 2026-08-10 at 16:40 +0000, Luke.Wildhardt@proton.me wrote: > Oops, forgot to reply all in my last message. >=20 > I did a quick test of the patch before I left this morning, the > freezing seems to gone, but when the GPU is under the same condition, > the stuttering is more uniform if that makes sense. Granted this was > only a 5 minute test but the freeze was rather reliable before, I can > do more testing later. That, unfortunately, indeed sounds as if we should go for the revert ASAP. >=20 > I know these things can be hard to describe, if that helps. If > there's any profiling I could do or detailed logging that would help > don't hesitate to ask. >=20 Would a screencast / filmed screen be helpful? IIRC Steam also has some fps counter etc in a submenu somewhere? In any case, if we want to go for the CFS rework in another respin, I suppose that it would be cool if @Tvrtko and you stay in contact Thank you very much for the report! Philipp