From: Maarten Lankhorst <dev@lankhorst.se>
To: intel-xe@lists.freedesktop.org
Cc: Maarten Lankhorst <dev@lankhorst.se>
Subject: [CI 00/13] Offload GGTT binding to migration engine.
Date: Fri, 4 Apr 2025 22:51:25 +0200 [thread overview]
Message-ID: <20250404205138.620455-1-dev@lankhorst.se> (raw)
Another way of tackling test failure.
Test to see if it passes CI, and for discussion.
Maarten Lankhorst (13):
drm/xe: Use xe_ggtt_map_bo_unlocked for resume
drm/xe: Add xe_ggtt_might_lock
drm/xe: Add xe_ggtt_alloc
drm/xe/display: Remove dereferences of ggtt for tile id
drm/xe/ggtt: Seperate flags and address in PTE encoding
drm/xe/display: Dont poke into GGTT internals to fill a DPT
drm/xe/display: Convert GGTT mapping to use pte_encode_flags
drm/xe: Remove pte_encode_bo callback
drm/xe: Implement a helper for reading out a GGTT PTE at a specified
offset
drm/xe: Add GGTT updates to migration engine
drm/xe: Convert xe_fb_pin to use a callback for insertion into GGTT
drm/xe: Allow for optimization of xe_ggtt_map_bo
drm/xe: Move struct xe_ggtt to xe_ggtt.c
drivers/gpu/drm/xe/display/xe_fb_pin.c | 151 ++++-----
drivers/gpu/drm/xe/display/xe_plane_initial.c | 6 +-
.../gpu/drm/xe/instructions/xe_mi_commands.h | 2 +
drivers/gpu/drm/xe/tests/xe_migrate.c | 75 +++++
drivers/gpu/drm/xe/xe_bo.c | 2 +-
drivers/gpu/drm/xe/xe_bo_evict.c | 4 +-
drivers/gpu/drm/xe/xe_ggtt.c | 289 +++++++++++++++---
drivers/gpu/drm/xe/xe_ggtt.h | 21 +-
drivers/gpu/drm/xe/xe_ggtt_types.h | 53 +---
drivers/gpu/drm/xe/xe_migrate.c | 87 ++++++
drivers/gpu/drm/xe/xe_migrate.h | 12 +
drivers/gpu/drm/xe/xe_tile.c | 6 +-
12 files changed, 517 insertions(+), 191 deletions(-)
--
2.45.2
next reply other threads:[~2025-04-04 20:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-04 20:51 Maarten Lankhorst [this message]
2025-04-04 20:51 ` [CI 01/13] drm/xe: Use xe_ggtt_map_bo_unlocked for resume Maarten Lankhorst
2025-04-04 20:51 ` [CI 02/13] drm/xe: Add xe_ggtt_might_lock Maarten Lankhorst
2025-04-04 20:51 ` [CI 03/13] drm/xe: Add xe_ggtt_alloc Maarten Lankhorst
2025-04-04 20:51 ` [CI 04/13] drm/xe/display: Remove dereferences of ggtt for tile id Maarten Lankhorst
2025-04-04 20:51 ` [CI 05/13] drm/xe/ggtt: Seperate flags and address in PTE encoding Maarten Lankhorst
2025-04-04 20:51 ` [CI 06/13] drm/xe/display: Dont poke into GGTT internals to fill a DPT Maarten Lankhorst
2025-04-04 20:51 ` [CI 07/13] drm/xe/display: Convert GGTT mapping to use pte_encode_flags Maarten Lankhorst
2025-04-04 20:51 ` [CI 08/13] drm/xe: Remove pte_encode_bo callback Maarten Lankhorst
2025-04-04 20:51 ` [CI 09/13] drm/xe: Implement a helper for reading out a GGTT PTE at a specified offset Maarten Lankhorst
2025-04-04 20:51 ` [CI 10/13] drm/xe: Add GGTT updates to migration engine Maarten Lankhorst
2025-04-04 20:51 ` [CI 11/13] drm/xe: Convert xe_fb_pin to use a callback for insertion into GGTT Maarten Lankhorst
2025-04-04 20:51 ` [CI 12/13] drm/xe: Allow for optimization of xe_ggtt_map_bo Maarten Lankhorst
2025-04-04 20:51 ` [CI 13/13] drm/xe: Move struct xe_ggtt to xe_ggtt.c Maarten Lankhorst
2025-04-04 22:20 ` ✓ CI.Patch_applied: success for Offload GGTT binding to migration engine Patchwork
2025-04-04 22:20 ` ✗ CI.checkpatch: warning " Patchwork
2025-04-04 22:21 ` ✗ CI.KUnit: 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=20250404205138.620455-1-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox