From: Matthew Auld <matthew.auld@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [PATCH v2 0/3] PM notifier
Date: Wed, 16 Apr 2025 16:09:14 +0100 [thread overview]
Message-ID: <20250416150913.434369-5-matthew.auld@intel.com> (raw)
Hook into the PM notifier for VRAM eviction (and pinned handling) prior to
s3/s4. Currently we are hitting issues with allocating large amounts of
system memory directly in the .suspend() callback.
v2:
- Improve the pinned handling and make the shared dma-resv more robust
(Thomas).
--
2.49.0
next reply other threads:[~2025-04-16 15:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 15:09 Matthew Auld [this message]
2025-04-16 15:09 ` [PATCH v2 1/3] drm/xe: evict user memory in PM notifier Matthew Auld
2025-04-16 15:09 ` [PATCH v2 2/3] drm/xe: share bo dma-resv with backup object Matthew Auld
2025-04-16 15:43 ` Thomas Hellström
2025-04-17 8:45 ` Matthew Auld
2025-04-22 7:01 ` Thomas Hellström
2025-04-16 15:09 ` [PATCH v2 3/3] drm/xe: handle pinned memory in PM notifier Matthew Auld
2025-04-16 15:45 ` Thomas Hellström
2025-04-16 16:23 ` ✓ Xe.CI.BAT: success for PM notifier (rev2) Patchwork
2025-04-16 23:44 ` ✗ Xe.CI.Full: failure " Patchwork
2025-04-22 11:31 ` ✓ CI.Patch_applied: success for PM notifier (rev3) Patchwork
2025-04-22 11:31 ` ✓ CI.checkpatch: " Patchwork
2025-04-22 11:33 ` ✓ CI.KUnit: " Patchwork
2025-04-22 11:41 ` ✓ CI.Build: " Patchwork
2025-04-22 11:43 ` ✗ CI.Hooks: failure " Patchwork
2025-04-22 11:44 ` ✓ CI.checksparse: success " Patchwork
2025-04-22 12:04 ` ✓ Xe.CI.BAT: " Patchwork
2025-04-22 14:29 ` ✗ Xe.CI.Full: failure " Patchwork
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=20250416150913.434369-5-matthew.auld@intel.com \
--to=matthew.auld@intel.com \
--cc=intel-xe@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox