From: Mirian Shilakadze <mirian.shilakadze@virtuozzo.com>
To: khorenko@virtuozzo.com
Cc: devel@openvz.org
Subject: [Devel] [PATCH hci-8.1 0/1] drm/amdgpu: fix init ordering in amdgpu_vram_mgr_init()
Date: Fri, 6 Nov 2026 18:55:18 +0400 [thread overview]
Message-ID: <20261106145524.96305-1-mirian.shilakadze@virtuozzo.com> (raw)
Backport of the upstream stable fix e773798e14ac ("drm/amdgpu: Fix
init ordering in amdgpu_vram_mgr_init()"). It registers the dmem
region after the VRAM manager lists and buddy allocator are set up, so
a failed registration leaves a manager that can be torn down safely.
It is a clean cherry-pick, the changed lines are the same as upstream,
and it only moves the registration down, nothing else changes.
Not run: we have no node with an AMD GPU. Build-tested only,
amdgpu_vram_mgr.o compiles with the 211.52.1.22.19 config.
As far as I can tell from reading the code, the crash described
upstream cannot be triggered in our kernel. amdgpu_ttm_fini() is only
reached from the GMC block sw_fini, and amdgpu_device_ip_fini() skips
a block whose sw_init failed, so a failed registration just fails
the probe.
https://virtuozzo.atlassian.net/browse/VSTOR-153702
Thomas Hellström (1):
ms/drm/amdgpu: Fix init ordering in amdgpu_vram_mgr_init()
drivers/gpu/drm/amd/amdgpu/amdgpu_vram_mgr.c | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
--
2.43.0
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
next reply other threads:[~2026-11-06 14:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 14:55 Mirian Shilakadze [this message]
2026-11-06 14:55 ` [Devel] [PATCH hci-8.1 1/1] ms/drm/amdgpu: Fix " Mirian Shilakadze
2026-11-06 15:00 ` no-reply
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=20261106145524.96305-1-mirian.shilakadze@virtuozzo.com \
--to=mirian.shilakadze@virtuozzo.com \
--cc=devel@openvz.org \
--cc=khorenko@virtuozzo.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