From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: intel-xe@lists.freedesktop.org
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Subject: [PATCH v2 0/3] drm/xe: Allow pinning of VRAM dma-bufs
Date: Thu, 18 Sep 2025 11:22:04 +0200 [thread overview]
Message-ID: <20250918092207.54472-1-thomas.hellstrom@linux.intel.com> (raw)
Three patches that together allow pinning of VRAM dma-bufs.
Patch 1 and 2 deals with backing those bos up on suspend,
Patch 3 implements the pinning and suggests a path to
a flexible cgroups accounting, on top of the cgroups
accounting we already have.
v2:
- Ensure content survives suspend and resume (Matt Auld)
- Update test comments (Niranjana)
Thomas Hellström (3):
drm/xe: Don't copy pinned kernel bos twice on suspend
drm/xe: Pre-allocate system memory for pinned external bos in the pm
notfier
drm/xe/dma-buf: Allow pinning of p2p dma-buf
drivers/gpu/drm/xe/tests/xe_dma_buf.c | 17 +++++++++--
drivers/gpu/drm/xe/xe_bo_evict.c | 13 +++++++--
drivers/gpu/drm/xe/xe_dma_buf.c | 41 +++++++++++++++++----------
3 files changed, 52 insertions(+), 19 deletions(-)
--
2.51.0
next reply other threads:[~2025-09-18 9:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 9:22 Thomas Hellström [this message]
2025-09-18 9:22 ` [PATCH v2 1/3] drm/xe: Don't copy pinned kernel bos twice on suspend Thomas Hellström
2025-09-18 9:38 ` Matthew Auld
2025-09-18 9:22 ` [PATCH v2 2/3] drm/xe: Pre-allocate system memory for pinned external bos in the pm notfier Thomas Hellström
2025-09-18 9:52 ` Matthew Auld
2025-09-18 9:22 ` [PATCH v2 3/3] drm/xe/dma-buf: Allow pinning of p2p dma-buf Thomas Hellström
2025-09-18 16:10 ` Simona Vetter
2025-09-22 9:11 ` Maarten Lankhorst
2025-09-18 9:40 ` ✓ CI.KUnit: success for drm/xe: Allow pinning of VRAM dma-bufs Patchwork
2025-09-18 10:12 ` ✓ Xe.CI.BAT: " Patchwork
2025-09-18 17:28 ` ✗ Xe.CI.Full: failure " Patchwork
2025-09-22 12:27 ` 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=20250918092207.54472-1-thomas.hellstrom@linux.intel.com \
--to=thomas.hellstrom@linux.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