Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: stuart.summers@intel.com, francois.dugast@intel.com
Subject: [PATCH v2 0/7] Pagefault refactor
Date: Fri, 24 Oct 2025 11:04:07 -0700	[thread overview]
Message-ID: <20251024180414.1379284-1-matthew.brost@intel.com> (raw)

We likely need multiple page fault producers feeding into a common
consumer backend. Additionally, our current page fault work queue
design—being per-GT rather than per-device—makes little sense. Clean up
pagefault handling with clear layers.

Matt

Matthew Brost (7):
  drm/xe: Stub out new pagefault layer
  drm/xe: Implement xe_pagefault_init
  drm/xe: Implement xe_pagefault_reset
  drm/xe: Implement xe_pagefault_handler
  drm/xe: Implement xe_pagefault_queue_work
  drm/xe: Add xe_guc_pagefault layer
  drm/xe: Remove unused GT page fault code

 drivers/gpu/drm/xe/Makefile             |   3 +-
 drivers/gpu/drm/xe/xe_device.c          |   5 +
 drivers/gpu/drm/xe/xe_device_types.h    |  11 +
 drivers/gpu/drm/xe/xe_gt.c              |   8 +-
 drivers/gpu/drm/xe/xe_gt_pagefault.c    | 679 ------------------------
 drivers/gpu/drm/xe/xe_gt_pagefault.h    |  19 -
 drivers/gpu/drm/xe/xe_gt_types.h        |  65 ---
 drivers/gpu/drm/xe/xe_guc_ct.c          |   6 +-
 drivers/gpu/drm/xe/xe_guc_pagefault.c   |  95 ++++
 drivers/gpu/drm/xe/xe_guc_pagefault.h   |  15 +
 drivers/gpu/drm/xe/xe_pagefault.c       | 436 +++++++++++++++
 drivers/gpu/drm/xe/xe_pagefault.h       |  19 +
 drivers/gpu/drm/xe/xe_pagefault_types.h | 136 +++++
 drivers/gpu/drm/xe/xe_svm.c             |   3 +-
 drivers/gpu/drm/xe/xe_vm.c              |   1 -
 15 files changed, 723 insertions(+), 778 deletions(-)
 delete mode 100644 drivers/gpu/drm/xe/xe_gt_pagefault.c
 delete mode 100644 drivers/gpu/drm/xe/xe_gt_pagefault.h
 create mode 100644 drivers/gpu/drm/xe/xe_guc_pagefault.c
 create mode 100644 drivers/gpu/drm/xe/xe_guc_pagefault.h
 create mode 100644 drivers/gpu/drm/xe/xe_pagefault.c
 create mode 100644 drivers/gpu/drm/xe/xe_pagefault.h
 create mode 100644 drivers/gpu/drm/xe/xe_pagefault_types.h

-- 
2.34.1


             reply	other threads:[~2025-10-24 18:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-24 18:04 Matthew Brost [this message]
2025-10-24 18:04 ` [PATCH v2 1/7] drm/xe: Stub out new pagefault layer Matthew Brost
2025-10-24 18:35   ` Summers, Stuart
2025-10-24 18:04 ` [PATCH v2 2/7] drm/xe: Implement xe_pagefault_init Matthew Brost
2025-10-24 18:55   ` Summers, Stuart
2025-10-24 19:18     ` Matthew Brost
2025-10-24 21:48       ` Matthew Brost
2025-10-24 18:04 ` [PATCH v2 3/7] drm/xe: Implement xe_pagefault_reset Matthew Brost
2025-10-24 18:04 ` [PATCH v2 4/7] drm/xe: Implement xe_pagefault_handler Matthew Brost
2025-10-24 18:04 ` [PATCH v2 5/7] drm/xe: Implement xe_pagefault_queue_work Matthew Brost
2025-10-24 18:04 ` [PATCH v2 6/7] drm/xe: Add xe_guc_pagefault layer Matthew Brost
2025-10-24 18:04 ` [PATCH v2 7/7] drm/xe: Remove unused GT page fault code Matthew Brost
2025-10-24 18:10 ` ✗ CI.checkpatch: warning for Pagefault refactor Patchwork
2025-10-24 18:11 ` ✓ CI.KUnit: success " Patchwork
2025-10-24 19:04 ` ✗ Xe.CI.BAT: failure " Patchwork
2025-10-25  7:17 ` ✗ 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=20251024180414.1379284-1-matthew.brost@intel.com \
    --to=matthew.brost@intel.com \
    --cc=francois.dugast@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=stuart.summers@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