Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: intel-xe@lists.freedesktop.org
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	"Matthew Brost" <matthew.brost@intel.com>,
	"Matthew Auld" <matthew.auld@intel.com>
Subject: [PATCH 0/2] Suspend improvements
Date: Thu, 18 Sep 2025 16:28:46 +0200	[thread overview]
Message-ID: <20250918142848.21807-1-thomas.hellstrom@linux.intel.com> (raw)

Two patches to improve suspend handling and code:

First patch takes the validation lock around user-space eviction. This
minimizes the number of bo locks held by racing processes and
therefore the likelyhood of a system bo being available for shrinking
if needed.

The second patch annotates the pm_block completion to avoid hard-to
track down suspend deadlocks moving forward.

Thomas Hellström (2):
  drm/xe/pm: Hold the validation lock around evicting user-space bos for
    suspend
  drm/xe/pm: Add lockdep annotation for the pm_block completion

 drivers/gpu/drm/xe/xe_exec.c |  3 +-
 drivers/gpu/drm/xe/xe_pm.c   | 66 ++++++++++++++++++++++++++++++++++++
 drivers/gpu/drm/xe/xe_pm.h   |  2 ++
 drivers/gpu/drm/xe/xe_vm.c   |  2 ++
 4 files changed, 72 insertions(+), 1 deletion(-)

-- 
2.51.0


             reply	other threads:[~2025-09-18 14:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-18 14:28 Thomas Hellström [this message]
2025-09-18 14:28 ` [PATCH 1/2] drm/xe/pm: Hold the validation lock around evicting user-space bos for suspend Thomas Hellström
2025-09-19 10:13   ` Matthew Auld
2025-09-18 14:28 ` [PATCH 2/2] drm/xe/pm: Add lockdep annotation for the pm_block completion Thomas Hellström
2025-09-19 11:00   ` Matthew Auld
2025-09-19 11:04     ` Thomas Hellström
2025-09-18 16:03 ` ✓ CI.KUnit: success for Suspend improvements Patchwork
2025-09-18 16:42 ` ✓ Xe.CI.BAT: " Patchwork
2025-09-19  1:17 ` ✗ Xe.CI.Full: failure " Patchwork
2025-09-23 12:37   ` Thomas Hellström

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=20250918142848.21807-1-thomas.hellstrom@linux.intel.com \
    --to=thomas.hellstrom@linux.intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.auld@intel.com \
    --cc=matthew.brost@intel.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