Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [RFC PATCH 0/3] Syncs vs async exec/bind uAPI change
Date: Wed,  6 Dec 2023 22:03:48 -0800	[thread overview]
Message-ID: <20231207060351.438855-1-matthew.brost@intel.com> (raw)

IGT changes for Xe uAPI changes [1].

A little more cleanup should be done but enough to get all IGTs passing.
Will finish cleanup in another rev or a follow up series.

Matt

[1] https://patchwork.freedesktop.org/series/127472/

Matthew Brost (3):
  xe_vm: Add section to test zero number of VM binds
  xe_exec_basic: Add section to test zero number of BB in exec IOCTL
  drm-uapi/xe: Uniform async vs sync handling

 benchmarks/gem_wsim.c                |  13 ++-
 include/drm-uapi/xe_drm.h            |  70 +++++++++------
 lib/igt_fb.c                         |   2 +-
 lib/intel_batchbuffer.c              |   7 +-
 lib/intel_compute.c                  |   2 +-
 lib/intel_ctx.c                      |   4 +-
 lib/xe/xe_ioctl.c                    |  66 +++++++-------
 lib/xe/xe_ioctl.h                    |  11 +--
 lib/xe/xe_query.c                    |   3 +-
 lib/xe/xe_spin.c                     |   8 +-
 lib/xe/xe_util.c                     |   4 +-
 tests/intel/xe_access_counter.c      |   2 +-
 tests/intel/xe_ccs.c                 |   4 +-
 tests/intel/xe_copy_basic.c          |   2 +-
 tests/intel/xe_create.c              |   6 +-
 tests/intel/xe_dma_buf_sync.c        |   4 +-
 tests/intel/xe_drm_fdinfo.c          |   8 +-
 tests/intel/xe_evict.c               |  37 ++++----
 tests/intel/xe_evict_ccs.c           |   2 +-
 tests/intel/xe_exec_balancer.c       |  19 ++---
 tests/intel/xe_exec_basic.c          | 118 +++++++++++++++++++++++--
 tests/intel/xe_exec_compute_mode.c   |  11 ++-
 tests/intel/xe_exec_fault_mode.c     |   9 +-
 tests/intel/xe_exec_queue_property.c |   2 +-
 tests/intel/xe_exec_reset.c          |  27 +++---
 tests/intel/xe_exec_store.c          |  18 ++--
 tests/intel/xe_exec_threads.c        |  26 +++---
 tests/intel/xe_exercise_blt.c        |   2 +-
 tests/intel/xe_huc_copy.c            |   2 +-
 tests/intel/xe_intel_bb.c            |   2 +-
 tests/intel/xe_noexec_ping_pong.c    |   6 +-
 tests/intel/xe_pat.c                 |   4 +-
 tests/intel/xe_perf_pmu.c            |  12 +--
 tests/intel/xe_pm.c                  |   6 +-
 tests/intel/xe_pm_residency.c        |   4 +-
 tests/intel/xe_spin_batch.c          |   4 +-
 tests/intel/xe_vm.c                  | 123 ++++++++++++++++++++-------
 tests/intel/xe_waitfence.c           |   8 +-
 38 files changed, 412 insertions(+), 246 deletions(-)

-- 
2.34.1

             reply	other threads:[~2023-12-07  6:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-07  6:03 Matthew Brost [this message]
2023-12-07  6:03 ` [igt-dev] [RFC PATCH 1/3] xe_vm: Add section to test zero number of VM binds Matthew Brost
2023-12-07  6:03 ` [igt-dev] [RFC PATCH 2/3] xe_exec_basic: Add section to test zero number of BB in exec IOCTL Matthew Brost
2023-12-07  6:03 ` [igt-dev] [RFC PATCH 3/3] drm-uapi/xe: Uniform async vs sync handling Matthew Brost
2023-12-07 19:59   ` Rodrigo Vivi
2023-12-07  7:36 ` [igt-dev] ✗ CI.xeBAT: failure for Syncs vs async exec/bind uAPI change 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=20231207060351.438855-1-matthew.brost@intel.com \
    --to=matthew.brost@intel.com \
    --cc=igt-dev@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