From: Maarten Lankhorst <dev@lankhorst.se>
To: intel-xe@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org, Maarten Lankhorst <dev@lankhorst.se>
Subject: [PATCH v3 0/6] drm/xe: More BIOS FB takeover fixes
Date: Mon, 20 Jul 2026 18:08:06 +0200 [thread overview]
Message-ID: <20260720160805.380356-8-dev@lankhorst.se> (raw)
Compared to previous version, fix the stolen oops and create
and use xe_ggtt_reserve_area instead of xe_ggtt_insert_node_at.
Reserve the original GGTT area of the original mapping, and remove
the code that was required to deal with the fact that previously
this was not done.
Maarten Lankhorst (6):
drm/xe/ggtt: Add xe_ggtt_reserve_area
drm/xe/ggtt: Add xe_ggtt_node_remove_noclear
drm/xe/display: Reserve the original GGTT space before creating a bo
drm/xe/display: Use the correct calculation for phys_base on
integrated
drm/xe/display: Remove duplicated code
drm/xe/ggtt: Remove xe_ggtt_insert_bo_at
drivers/gpu/drm/xe/display/xe_initial_plane.c | 41 +++----
drivers/gpu/drm/xe/xe_bo.c | 8 +-
drivers/gpu/drm/xe/xe_ggtt.c | 115 ++++++++++++++----
drivers/gpu/drm/xe/xe_ggtt.h | 5 +-
4 files changed, 110 insertions(+), 59 deletions(-)
--
2.53.0
next reply other threads:[~2026-07-20 16:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 16:08 Maarten Lankhorst [this message]
2026-07-20 16:08 ` [PATCH v3 1/6] drm/xe/ggtt: Add xe_ggtt_reserve_area Maarten Lankhorst
2026-07-20 16:08 ` [PATCH v3 2/6] drm/xe/ggtt: Add xe_ggtt_node_remove_noclear Maarten Lankhorst
2026-07-20 16:08 ` [PATCH v3 3/6] drm/xe/display: Reserve the original GGTT space before creating a bo Maarten Lankhorst
2026-07-20 16:08 ` [PATCH v3 4/6] drm/xe/display: Use the correct calculation for phys_base on integrated Maarten Lankhorst
2026-07-20 16:08 ` [PATCH v3 5/6] drm/xe/display: Remove duplicated code Maarten Lankhorst
2026-07-20 16:08 ` [PATCH v3 6/6] drm/xe/ggtt: Remove xe_ggtt_insert_bo_at Maarten Lankhorst
2026-07-20 20:05 ` ✓ i915.CI.BAT: success for drm/xe: More BIOS FB takeover fixes (rev3) Patchwork
2026-07-21 3:23 ` ✗ i915.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=20260720160805.380356-8-dev@lankhorst.se \
--to=dev@lankhorst.se \
--cc=intel-gfx@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