All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Fixes for DRM node limits
Date: Thu, 19 Sep 2024 09:04:39 -0500	[thread overview]
Message-ID: <286c7953-2bdd-4d8a-918d-e31de8120d7a@amd.com> (raw)

Hi,

With systems that have 8 GPUs nodes + an integrated BMC, the BMC can't 
work properly because of limits of DRM nodes in the kernel.

This is fixed in Linus tree with these commits:

Can you please backport to 6.6.y and later?

commit 5fbca8b48b30 ("drm: Use XArray instead of IDR for minors")
commit 45c4d994b82b ("accel: Use XArray instead of IDR for minors")
commit 071d583e01c8 ("drm: Expand max DRM device number to full MINORBITS")

Thanks,

             reply	other threads:[~2024-09-19 14:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-19 14:04 Mario Limonciello [this message]
2024-09-23  8:49 ` Fixes for DRM node limits Sasha Levin

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=286c7953-2bdd-4d8a-918d-e31de8120d7a@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=stable@vger.kernel.org \
    /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.