From: Francois Dugast <francois.dugast@intel.com>
To: Matthew Brost <matthew.brost@intel.com>
Cc: <intel-xe@lists.freedesktop.org>, <stuart.summers@intel.com>
Subject: Re: [PATCH v4 0/7] Pagefault refactor
Date: Tue, 4 Nov 2025 17:24:46 +0100 [thread overview]
Message-ID: <aQoozpynadgwyfP0@fdugast-desk> (raw)
In-Reply-To: <20251031165416.2871503-1-matthew.brost@intel.com>
On Fri, Oct 31, 2025 at 09:54:09AM -0700, Matthew Brost wrote:
> 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
I ran some HPC performance test with the series, feel free to add:
Tested-by: Francois Dugast <francois.dugast@intel.com>
prev parent reply other threads:[~2025-11-04 16:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 16:54 [PATCH v4 0/7] Pagefault refactor Matthew Brost
2025-10-31 16:54 ` [PATCH v4 1/7] drm/xe: Stub out new pagefault layer Matthew Brost
2025-11-04 3:57 ` Lucas De Marchi
2025-10-31 16:54 ` [PATCH v4 2/7] drm/xe: Implement xe_pagefault_init Matthew Brost
2025-11-03 13:22 ` Francois Dugast
2025-11-03 17:07 ` Matthew Brost
2025-10-31 16:54 ` [PATCH v4 3/7] drm/xe: Implement xe_pagefault_reset Matthew Brost
2025-11-04 4:02 ` Lucas De Marchi
2025-10-31 16:54 ` [PATCH v4 4/7] drm/xe: Implement xe_pagefault_handler Matthew Brost
2025-10-31 16:54 ` [PATCH v4 5/7] drm/xe: Implement xe_pagefault_queue_work Matthew Brost
2025-11-04 15:01 ` Lucas De Marchi
2025-11-04 15:50 ` Matthew Brost
2025-10-31 16:54 ` [PATCH v4 6/7] drm/xe: Add xe_guc_pagefault layer Matthew Brost
2025-11-03 18:28 ` Lucas De Marchi
2025-11-03 18:56 ` Matthew Brost
2025-11-03 19:11 ` Lucas De Marchi
2025-11-03 19:15 ` Matthew Brost
2025-11-04 16:12 ` Lucas De Marchi
2025-10-31 16:54 ` [PATCH v4 7/7] drm/xe: Remove unused GT page fault code Matthew Brost
2025-11-04 16:13 ` Lucas De Marchi
2025-10-31 18:00 ` ✗ CI.checkpatch: warning for Pagefault refactor (rev3) Patchwork
2025-10-31 18:01 ` ✓ CI.KUnit: success " Patchwork
2025-10-31 19:04 ` ✓ Xe.CI.BAT: " Patchwork
2025-11-01 6:59 ` ✗ Xe.CI.Full: failure " Patchwork
2025-11-04 16:24 ` Francois Dugast [this message]
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=aQoozpynadgwyfP0@fdugast-desk \
--to=francois.dugast@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@intel.com \
--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