All Virtuozzo development lists (kernel + QEMU)
 help / color / mirror / Atom feed
From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: Mirian Shilakadze <mirian.shilakadze@virtuozzo.com>
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH hci-8.1 0/1] drm/amdgpu: fix init ordering in amdgpu_vram_mgr_init()
Date: Thu, 12 Nov 2026 14:32:03 +0100	[thread overview]
Message-ID: <179449032345.4060562.12647834466616155886.b4-ty@b4> (raw)
In-Reply-To: <20261106145524.96305-1-mirian.shilakadze@virtuozzo.com>

On Fri, 06 Nov 2026 18:55:18 +0400, Mirian Shilakadze wrote:
> drm/amdgpu: fix init ordering in amdgpu_vram_mgr_init()
> 
> 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.
> 
> [...]

Applied to branch-rh10-6.12.0-211.52.1.22.x.vz10-ovz, will be released in rh10-6.12.0-211.52.1.22.21.vz10, thanks!

[1/1] ms/drm/amdgpu: Fix init ordering in amdgpu_vram_mgr_init()
      https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/ffbc4c6f4d0b

-- 
Konstantin Khorenko,
Virtuozzo Linux Kernel Team


_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel

      parent reply	other threads:[~2026-11-12 13:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-06 14:55 Mirian Shilakadze
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
2026-11-12 13:31   ` Konstantin Khorenko
2026-11-12 13:31 ` [Devel] [PATCH hci-8.1 0/1] drm/amdgpu: fix " Konstantin Khorenko
2026-11-12 13:32 ` Konstantin Khorenko [this message]

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=179449032345.4060562.12647834466616155886.b4-ty@b4 \
    --to=khorenko@virtuozzo.com \
    --cc=devel@openvz.org \
    --cc=mirian.shilakadze@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.