Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Maarten Lankhorst <dev@lankhorst.se>
To: intel-xe@lists.freedesktop.org
Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>,
	Maarten Lankhorst <dev@lankhorst.se>
Subject: [PATCH v5 0/5] drm/xe: Privatize struct xe_ggtt.
Date: Mon, 19 Jan 2026 13:50:56 +0100	[thread overview]
Message-ID: <20260119125101.277182-1-dev@lankhorst.se> (raw)

Clean up SRIOV-VF handling and pop the balloons, move struct xe_ggtt to xe_ggtt.c,
and clean up the API's slightly by removing a separate xe_gtt_node_init() step.

This makes the xe_ggtt_node_allocated obsolete, as we only create allocated nodes now.

Changes since last version:
- Some small fixes and cleanups.
- Didn't rename xe_ggtt_node_insert, as I feel the correct name would
  then be xe_ggtt_insert_ggtt_node().

Maarten Lankhorst (5):
  drm/xe: Make xe_ggtt_node offset relative to starting offset
  drm/xe: Rewrite GGTT VF initialization
  drm/xe: Move struct xe_ggtt to xe_ggtt.c
  drm/xe: Make xe_ggtt_node_insert return a node
  drm/xe: Remove xe_ggtt_node_allocated

 drivers/gpu/drm/xe/display/xe_fb_pin.c      |   3 +-
 drivers/gpu/drm/xe/tests/xe_guc_buf_kunit.c |   6 +-
 drivers/gpu/drm/xe/xe_device_types.h        |   2 -
 drivers/gpu/drm/xe/xe_ggtt.c                | 339 ++++++++------------
 drivers/gpu/drm/xe/xe_ggtt.h                |  12 +-
 drivers/gpu/drm/xe/xe_ggtt_types.h          |  60 +---
 drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c  |  36 +--
 drivers/gpu/drm/xe/xe_gt_sriov_vf.c         |  27 +-
 drivers/gpu/drm/xe/xe_tile_sriov_vf.c       | 198 +-----------
 drivers/gpu/drm/xe/xe_tile_sriov_vf.h       |   3 -
 10 files changed, 175 insertions(+), 511 deletions(-)

-- 
2.51.0


             reply	other threads:[~2026-01-19 12:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-19 12:50 Maarten Lankhorst [this message]
2026-01-19 12:50 ` [PATCH v5 1/5] drm/xe: Make xe_ggtt_node offset relative to starting offset Maarten Lankhorst
2026-01-20 15:27   ` Michal Wajdeczko
2026-01-19 12:50 ` [PATCH v5 2/5] drm/xe: Rewrite GGTT VF initialization Maarten Lankhorst
2026-01-20 16:11   ` Michal Wajdeczko
2026-01-20 18:23     ` Maarten Lankhorst
2026-01-19 12:50 ` [PATCH v5 3/5] drm/xe: Move struct xe_ggtt to xe_ggtt.c Maarten Lankhorst
2026-01-19 12:51 ` [PATCH v5 4/5] drm/xe: Make xe_ggtt_node_insert return a node Maarten Lankhorst
2026-01-20 16:31   ` Michal Wajdeczko
2026-01-19 12:51 ` [PATCH v5 5/5] drm/xe: Remove xe_ggtt_node_allocated Maarten Lankhorst

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=20260119125101.277182-1-dev@lankhorst.se \
    --to=dev@lankhorst.se \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=michal.wajdeczko@intel.com \
    /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