From: Maarten Lankhorst <dev@lankhorst.se>
To: intel-xe@lists.freedesktop.org
Cc: Maarten Lankhorst <dev@lankhorst.se>
Subject: [PATCH v2 0/7] drm/xe: Privatize struct xe_ggtt_node.
Date: Thu, 8 Jan 2026 11:10:15 +0100 [thread overview]
Message-ID: <20260108101014.579906-9-dev@lankhorst.se> (raw)
I'm trying to fix the problem that GGTT can be moved on VF's. The easiest
solution is resizing the GGTT to be as big as can be allowed, and provide
a variable ggtt->start. To facilitate this, the first step is avoid
the rest of the code from looking at drm_mm_node directly,
this will make it possible to change its start offset in the next series.
Maarten Lankhorst (7):
drm/xe: Start using ggtt->start in preparation of balloon removal
drm/xe: Convert xe_fb_pin to use a callback for insertion into GGTT
drm/xe: Add xe_ggtt_node_addr() to avoid dereferencing xe_ggtt_node
drm/xe/display: Avoid dereferencing xe_ggtt_node
drm/xe: Do not dereference ggtt_node in xe_bo.c
drm/xe: Improve xe_gt_sriov_pf_config GGTT handling
drm/xe: Privatize xe_ggtt_node
.../gpu/drm/xe/compat-i915-headers/i915_vma.h | 4 +-
drivers/gpu/drm/xe/display/xe_fb_pin.c | 104 ++++-----
drivers/gpu/drm/xe/display/xe_stolen.c | 2 +-
drivers/gpu/drm/xe/tests/xe_guc_buf_kunit.c | 2 +-
drivers/gpu/drm/xe/xe_bo.c | 6 +-
drivers/gpu/drm/xe/xe_bo.h | 8 +-
drivers/gpu/drm/xe/xe_ggtt.c | 212 +++++++++++++-----
drivers/gpu/drm/xe/xe_ggtt.h | 14 +-
drivers/gpu/drm/xe/xe_ggtt_types.h | 32 +--
drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c | 19 +-
10 files changed, 254 insertions(+), 149 deletions(-)
--
2.51.0
next reply other threads:[~2026-01-08 10:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 10:10 Maarten Lankhorst [this message]
2026-01-08 10:10 ` [PATCH v2 1/7] drm/xe: Start using ggtt->start in preparation of balloon removal Maarten Lankhorst
2026-01-08 10:10 ` [PATCH v2 2/7] drm/xe: Convert xe_fb_pin to use a callback for insertion into GGTT Maarten Lankhorst
2026-01-08 10:10 ` [PATCH v2 3/7] drm/xe: Add xe_ggtt_node_addr() to avoid dereferencing xe_ggtt_node Maarten Lankhorst
2026-01-08 16:15 ` Matthew Brost
2026-01-08 10:10 ` [PATCH v2 4/7] drm/xe/display: Avoid " Maarten Lankhorst
2026-01-12 14:46 ` Rodrigo Vivi
2026-01-08 10:10 ` [PATCH v2 5/7] drm/xe: Do not dereference ggtt_node in xe_bo.c Maarten Lankhorst
2026-01-08 16:16 ` Matthew Brost
2026-01-08 10:10 ` [PATCH v2 6/7] drm/xe: Improve xe_gt_sriov_pf_config GGTT handling Maarten Lankhorst
2026-01-08 10:10 ` [PATCH v2 7/7] drm/xe: Privatize xe_ggtt_node Maarten Lankhorst
2026-01-08 10:40 ` ✗ CI.checkpatch: warning for drm/xe: Privatize struct xe_ggtt_node. (rev2) Patchwork
2026-01-08 10:41 ` ✓ CI.KUnit: success " Patchwork
2026-01-08 11:40 ` ✓ Xe.CI.BAT: " Patchwork
2026-01-08 14:19 ` ✓ Xe.CI.Full: " 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=20260108101014.579906-9-dev@lankhorst.se \
--to=dev@lankhorst.se \
--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 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.