From: Maarten Lankhorst <dev@lankhorst.se>
To: intel-xe@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org, Maarten Lankhorst <dev@lankhorst.se>
Subject: [PATCH v2 0/5] drm/xe: Make struct xe_ggtt private.
Date: Tue, 10 Jun 2025 09:02:34 +0200 [thread overview]
Message-ID: <20250610070241.875636-1-dev@lankhorst.se> (raw)
SRIOV-VF node shifting code uses a complicated system with balloons
to limit allocation and size. Since size never changes after init,
shifting can simply be done by taking the the GGTT lock.
First introduce a function to shift an entire GGTT, this removes the
need for the balloons, then also perform the display code pinning
through a callback, and finally privatize the struct.
No other users outside of xe_ggtt remain.
Maarten Lankhorst (4):
drm/xe: Start using ggtt->start in preparation of balloon removal
drm/xe: Rewrite GGTT VF initialisation
drm/xe: Convert xe_fb_pin to use a callback for insertion into GGTT
drm/xe: Move struct xe_ggtt to xe_ggtt.c
Tomasz Lis (1):
drm/mm: Introduce address space shifting
drivers/gpu/drm/drm_mm.c | 24 ++
drivers/gpu/drm/xe/Makefile | 3 +-
drivers/gpu/drm/xe/display/xe_fb_pin.c | 111 +++----
drivers/gpu/drm/xe/tests/xe_guc_buf_kunit.c | 2 +-
drivers/gpu/drm/xe/xe_ggtt.c | 336 ++++++++++----------
drivers/gpu/drm/xe/xe_ggtt.h | 14 +-
drivers/gpu/drm/xe/xe_ggtt_types.h | 53 +--
drivers/gpu/drm/xe/xe_sriov_vf.c | 4 +-
drivers/gpu/drm/xe/xe_tile_sriov_vf.c | 254 ---------------
drivers/gpu/drm/xe/xe_tile_sriov_vf.h | 18 --
include/drm/drm_mm.h | 1 +
11 files changed, 261 insertions(+), 559 deletions(-)
delete mode 100644 drivers/gpu/drm/xe/xe_tile_sriov_vf.c
delete mode 100644 drivers/gpu/drm/xe/xe_tile_sriov_vf.h
--
2.45.2
next reply other threads:[~2025-06-10 7:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 7:02 Maarten Lankhorst [this message]
2025-06-10 7:02 ` [PATCH v2 1/5] drm/mm: Introduce address space shifting Maarten Lankhorst
2025-06-10 7:02 ` [PATCH v2 2/5] drm/xe: Start using ggtt->start in preparation of balloon removal Maarten Lankhorst
2025-06-11 18:53 ` Summers, Stuart
2025-06-23 7:21 ` Maarten Lankhorst
2025-06-10 7:02 ` [PATCH v2 3/5] drm/xe: Rewrite GGTT VF initialisation Maarten Lankhorst
2025-06-10 7:02 ` [PATCH v2 4/5] drm/xe: Convert xe_fb_pin to use a callback for insertion into GGTT Maarten Lankhorst
2025-06-23 13:43 ` Juha-Pekka Heikkilä
2025-06-10 7:02 ` [PATCH v2 5/5] drm/xe: Move struct xe_ggtt to xe_ggtt.c Maarten Lankhorst
2025-06-10 7:10 ` ✓ CI.Patch_applied: success for drm/xe: Make struct xe_ggtt private. (rev2) Patchwork
2025-06-10 7:10 ` ✗ CI.checkpatch: warning " Patchwork
2025-06-10 7:11 ` ✓ CI.KUnit: success " Patchwork
2025-06-10 7:22 ` ✓ CI.Build: " Patchwork
2025-06-10 7:25 ` ✓ CI.Hooks: " Patchwork
2025-06-10 7:26 ` ✗ CI.checksparse: warning " Patchwork
2025-06-10 8:19 ` ✗ Xe.CI.BAT: failure " Patchwork
2025-06-10 9: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=20250610070241.875636-1-dev@lankhorst.se \
--to=dev@lankhorst.se \
--cc=dri-devel@lists.freedesktop.org \
--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