From: Matthew Brost <matthew.brost@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: thomas.hellstrom@linux.intel.com, matthew.auld@intel.com
Subject: [PATCH 0/2] Userptr fixes
Date: Thu, 20 Feb 2025 15:45:55 -0800 [thread overview]
Message-ID: <20250220234557.2613010-1-matthew.brost@intel.com> (raw)
Tested with below tests on BMG + CONFIG_DRM_XE_USERPTR_INVAL_INJECT
xe_exec_basic; xe_exec_compute_mode; xe_exec_fault_mode; xe_vm; xe_exec_threads
Including a patch from Matt Auld as it required for above test case to pass.
Matt
Matthew Auld (1):
drm/xe/userptr: fix EFAULT handling
Matthew Brost (1):
drm/xe: Userptr invalidation race with binds fixes
drivers/gpu/drm/xe/regs/xe_gtt_defs.h | 1 +
drivers/gpu/drm/xe/xe_pt.c | 86 +++++++++++++++++++--------
drivers/gpu/drm/xe/xe_pt_types.h | 1 -
drivers/gpu/drm/xe/xe_vm.c | 16 ++++-
4 files changed, 76 insertions(+), 28 deletions(-)
--
2.34.1
next reply other threads:[~2025-02-20 23:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 23:45 Matthew Brost [this message]
2025-02-20 23:45 ` [PATCH 1/2] drm/xe/userptr: fix EFAULT handling Matthew Brost
2025-02-21 8:57 ` Thomas Hellström
2025-02-20 23:45 ` [PATCH 2/2] drm/xe: Userptr invalidation race with binds fixes Matthew Brost
2025-02-21 11:34 ` Thomas Hellström
2025-02-21 14:43 ` Matthew Brost
2025-02-21 15:27 ` Thomas Hellström
2025-02-21 16:59 ` Matthew Brost
2025-02-24 8:06 ` Thomas Hellström
2025-02-20 23:50 ` ✓ CI.Patch_applied: success for Userptr fixes Patchwork
2025-02-20 23:50 ` ✗ CI.checkpatch: warning " Patchwork
2025-02-20 23:51 ` ✓ CI.KUnit: success " Patchwork
2025-02-21 0:08 ` ✓ CI.Build: " Patchwork
2025-02-21 0:10 ` ✓ CI.Hooks: " Patchwork
2025-02-21 0:12 ` ✓ CI.checksparse: " Patchwork
2025-02-21 0:31 ` ✓ Xe.CI.BAT: " Patchwork
2025-02-21 16:28 ` ✗ Xe.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=20250220234557.2613010-1-matthew.brost@intel.com \
--to=matthew.brost@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=thomas.hellstrom@linux.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