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: thomas.hellstrom@linux.intel.com, matthew.auld@intel.com
Subject: [PATCH v4 0/2] Userptr fixes
Date: Mon, 24 Feb 2025 09:01:07 -0800	[thread overview]
Message-ID: <20250224170109.3078314-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

Matt

Matthew Brost (2):
  drm/xe: Userptr invalidation race with binds fixes
  drm/xe: Add staging tree for VM binds

 drivers/gpu/drm/xe/xe_pt.c      | 79 ++++++++++++++++++++++-----------
 drivers/gpu/drm/xe/xe_pt_walk.c |  3 +-
 drivers/gpu/drm/xe/xe_pt_walk.h |  4 ++
 drivers/gpu/drm/xe/xe_vm.c      |  4 +-
 4 files changed, 60 insertions(+), 30 deletions(-)

-- 
2.34.1


             reply	other threads:[~2025-02-24 17:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-24 17:01 Matthew Brost [this message]
2025-02-24 17:01 ` [PATCH v4 1/2] drm/xe: Userptr invalidation race with binds fixes Matthew Brost
2025-02-25 14:30   ` Thomas Hellström
2025-02-25 17:45     ` Matthew Brost
2025-02-25 18:56       ` Thomas Hellström
2025-02-25 19:23         ` Matthew Brost
2025-02-25 20:06           ` Matthew Brost
2025-02-26 15:13             ` Thomas Hellström
2025-02-24 17:01 ` [PATCH v4 2/2] drm/xe: Add staging tree for VM binds Matthew Brost
2025-02-25  0:17 ` ✓ CI.Patch_applied: success for Userptr fixes Patchwork
2025-02-25  0:17 ` ✓ CI.checkpatch: " Patchwork
2025-02-25  0:18 ` ✓ CI.KUnit: " Patchwork
2025-02-25  0:35 ` ✓ CI.Build: " Patchwork
2025-02-25  0:37 ` ✓ CI.Hooks: " Patchwork
2025-02-25  0:38 ` ✓ CI.checksparse: " Patchwork
2025-02-25  0:58 ` ✓ Xe.CI.BAT: " Patchwork
2025-02-25  3:53 ` ✗ 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=20250224170109.3078314-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