From: Natalie Vock <natalie.vock@gmx.de>
To: "Mikhail Gavrilov" <mikhail.v.gavrilov@gmail.com>,
"Christian König" <Christian.Koenig@amd.com>,
"Deucher, Alexander" <Alexander.Deucher@amd.com>,
"amd-gfx list" <amd-gfx@lists.freedesktop.org>,
"Linux List Kernel Mailing" <linux-kernel@vger.kernel.org>,
"Linux regressions mailing list" <regressions@lists.linux.dev>
Subject: Re: [REGRESSION 7.2] drm/amdgpu: ~275 SDMA jobs per sparse VA bind since 4cdbba5a (RE Requiem 90->4 fps)
Date: Mon, 22 Jun 2026 07:44:02 +0200 [thread overview]
Message-ID: <c084c555-e4f4-48a6-9fad-175932acda01@gmx.de> (raw)
In-Reply-To: <CABXGCsOuCXr4R+WW60KNuWNS2MqzE9w6iv-t_ykbwmhqDSABAQ@mail.gmail.com>
On 6/21/26 22:55, Mikhail Gavrilov wrote:
> Hi Christian, Alex,
>
> git bisect points to
>
> 4cdbba5a16aa ("drm/amdgpu: restructure VM state machine v4")
>
> as the first bad commit (its parent tests fine) for a severe
> interactivity regression.
>
> It was merged during the current 7.2 merge window; it is not in any
> released kernel yet and will first appear in 7.2-rc1.
>
> Symptom: Resident Evil Requiem (re9.exe under VKD3D-Proton, RADV, RX
> 7900 XTX / Navi31, gfx11) drops from ~90 to 3-4 fps the instant the
> camera moves; still scenes are fine. The previous bisect point
> d352990bcaab is smooth.
I already fixed this in a patchset[1] that should be on its way - seems
like it didn't make it into rc1 at least?
Christian, Alex, can you make sure that the first patch from that set,
"drm/amdgpu: Only set bo->moved when the BO was actually moved", is
included in a -fixes PR for 7.2?
For the record, I intentionally did not include a Fixes: tag in this
patchset, because the commit was not merged anywhere but
amd-staging-drm-next at the point of writing, and the same commits in
amd-staging-drm-next and upstream have different SHAs. AFAIU, this also
prevents me from telling regzbot that a proper fix is underway for now.
Not sure if there's a workaround for this?
Best,
Natalie
[1]
https://lore.kernel.org/amd-gfx/20260529153051.973261-1-natalie.vock@gmx.de/
next prev parent reply other threads:[~2026-06-22 5:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-21 20:55 Mikhail Gavrilov
2026-06-22 5:44 ` Natalie Vock [this message]
2026-06-22 7:26 ` Mikhail Gavrilov
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=c084c555-e4f4-48a6-9fad-175932acda01@gmx.de \
--to=natalie.vock@gmx.de \
--cc=Alexander.Deucher@amd.com \
--cc=Christian.Koenig@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikhail.v.gavrilov@gmail.com \
--cc=regressions@lists.linux.dev \
/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®