intel-xe.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: <intel-xe@lists.freedesktop.org>
Cc: Matthew Brost <matthew.brost@intel.com>
Subject: [PATCH v2 0/6] Convert multiple bind ops to 1 job
Date: Tue, 14 May 2024 17:40:04 -0700	[thread overview]
Message-ID: <20240515004010.100091-1-matthew.brost@intel.com> (raw)

Continuation of merging parts of [1]. Patch #2 in this series is quite
large but unsure how to split the patch without breaking functionality.

Tested with [2].

v2:
 - Rebase
 - Add error injection patch
 - Fix dma-fence reservation for binds

Matt

[1] https://patchwork.freedesktop.org/series/125608/
[2] https://patchwork.freedesktop.org/series/129606/

Matthew Brost (6):
  drm/xe: s/xe_tile_migrate_engine/xe_tile_migrate_exec_queue
  drm/xe: Add xe_vm_pgtable_update_op to xe_vma_ops
  drm/xe: Convert multiple bind ops into single job
  drm/xe: Update VM trace events
  drm/xe: Update PT layer with better error handling
  drm/xe: Add VM bind IOCTL error injection

 drivers/gpu/drm/xe/xe_bo_types.h     |    2 +
 drivers/gpu/drm/xe/xe_device_types.h |   12 +
 drivers/gpu/drm/xe/xe_migrate.c      |  307 +++---
 drivers/gpu/drm/xe/xe_migrate.h      |   34 +-
 drivers/gpu/drm/xe/xe_pt.c           | 1286 +++++++++++++++++---------
 drivers/gpu/drm/xe/xe_pt.h           |   14 +-
 drivers/gpu/drm/xe/xe_pt_types.h     |   48 +
 drivers/gpu/drm/xe/xe_trace.h        |   10 +-
 drivers/gpu/drm/xe/xe_vm.c           |  647 +++++--------
 drivers/gpu/drm/xe/xe_vm.h           |    2 +
 drivers/gpu/drm/xe/xe_vm_types.h     |   53 +-
 11 files changed, 1360 insertions(+), 1055 deletions(-)

-- 
2.34.1


             reply	other threads:[~2024-05-15  0:39 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-15  0:40 Matthew Brost [this message]
2024-05-15  0:40 ` [PATCH v2 1/6] drm/xe: s/xe_tile_migrate_engine/xe_tile_migrate_exec_queue Matthew Brost
2024-05-15 20:56   ` Cavitt, Jonathan
2024-05-18  2:42   ` Zeng, Oak
2024-05-15  0:40 ` [PATCH v2 2/6] drm/xe: Add xe_vm_pgtable_update_op to xe_vma_ops Matthew Brost
2024-05-15 21:56   ` Cavitt, Jonathan
2024-05-15  0:40 ` [PATCH v2 3/6] drm/xe: Convert multiple bind ops into single job Matthew Brost
2024-05-15  0:40 ` [PATCH v2 4/6] drm/xe: Update VM trace events Matthew Brost
2024-05-15 20:59   ` Cavitt, Jonathan
2024-05-15  0:40 ` [PATCH v2 5/6] drm/xe: Update PT layer with better error handling Matthew Brost
2024-05-15  0:40 ` [PATCH v2 6/6] drm/xe: Add VM bind IOCTL error injection Matthew Brost
2024-05-15 21:29   ` Cavitt, Jonathan
2024-05-15 22:45     ` Matthew Brost
2024-05-15  0:44 ` ✓ CI.Patch_applied: success for Convert multiple bind ops to 1 job (rev2) Patchwork
2024-05-15  0:44 ` ✗ CI.checkpatch: warning " Patchwork
2024-05-15  0:45 ` ✓ CI.KUnit: success " Patchwork
2024-05-15  0:57 ` ✓ CI.Build: " Patchwork
2024-05-15  0:59 ` ✓ CI.Hooks: " Patchwork
2024-05-15  1:01 ` ✓ CI.checksparse: " Patchwork
2024-05-15  1:26 ` ✓ CI.BAT: " Patchwork
2024-05-15  2:53 ` ✗ CI.FULL: failure " Patchwork
2024-05-18  2:41 ` [PATCH v2 0/6] Convert multiple bind ops to 1 job Zeng, Oak

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=20240515004010.100091-1-matthew.brost@intel.com \
    --to=matthew.brost@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).