mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Philipp Stanner <phasta@mailbox.org>
To: Luke.Wildhardt@proton.me, Tvrtko Ursulin <tvrtko.ursulin@igalia.com>
Cc: Danilo Krummrich <dakr@kernel.org>,
	phasta@kernel.org,
	 "matthew.brost@intel.com" <matthew.brost@intel.com>,
	"ckoenig.leichtzumerken@gmail.com"
	<ckoenig.leichtzumerken@gmail.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
	"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [REGRESSION] drm/sched: FAIR policy causes serious performance degradation at max GPU load on 9070XT
Date: Tue, 11 Aug 2026 09:29:13 +0200	[thread overview]
Message-ID: <e343b5fb2034b56af9049df970b987b239aacde7.camel@mailbox.org> (raw)
In-Reply-To: <enK0t0JrZ3lr9gmgPwE_YaVJDy7K355Bs0xy0YNoVwujLHCGWNRXCjDOhYfiHNGN3pPDSlEUIz3_UkXmFNAJNXxrJOIwvzAG-k8_p_D5FOQ=@proton.me>

On Mon, 2026-08-10 at 16:40 +0000, Luke.Wildhardt@proton.me wrote:
> Oops, forgot to reply all in my last message.
> 
> 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.

> 
> 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.
> 

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


  reply	other threads:[~2026-08-11  7:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-08 23:33 Luke.Wildhardt
2026-08-10  8:28 ` Philipp Stanner
2026-08-10 12:45   ` Danilo Krummrich
2026-08-10 13:48     ` Tvrtko Ursulin
2026-08-10 16:40       ` Luke.Wildhardt
2026-08-11  7:29         ` Philipp Stanner [this message]
2026-08-11  7:49         ` Tvrtko Ursulin
2026-08-11 17:59         ` Luke.Wildhardt
2026-08-12 11:37           ` Tvrtko Ursulin
2026-08-12 11:58             ` Philipp Stanner
2026-08-12 12:29               ` Tvrtko Ursulin
2026-09-16  7:37                 ` Philipp Stanner
2026-08-12 15:12             ` Luke.Wildhardt
2026-08-13  6:42               ` Luke.Wildhardt
2026-08-13  7:58                 ` Tvrtko Ursulin
2026-08-13 14:27                   ` Luke.Wildhardt
2026-08-14  6:49                     ` Luke.Wildhardt
2026-08-14  8:32                     ` Feng, Kenneth
2026-08-10 11:36 ` Tvrtko Ursulin
2026-08-11  7:46 ` Tvrtko Ursulin
2026-08-12  4:52   ` Luke.Wildhardt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e343b5fb2034b56af9049df970b987b239aacde7.camel@mailbox.org \
    --to=phasta@mailbox.org \
    --cc=Luke.Wildhardt@proton.me \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=ckoenig.leichtzumerken@gmail.com \
    --cc=dakr@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.brost@intel.com \
    --cc=phasta@kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=tvrtko.ursulin@igalia.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®