From: Matthew Brost <matthew.brost@intel.com>
To: <intel-xe@lists.freedesktop.org>
Subject: [Intel-xe] [RFC PATCH 0/7] Syncs vs async exec/bind uAPI change
Date: Wed, 6 Dec 2023 21:57:22 -0800 [thread overview]
Message-ID: <20231207055729.438642-1-matthew.brost@intel.com> (raw)
Last patch should explain it nicely, built on top of [1].
Backwards breaking, IGT change will be on list shortly.
Matt
[1] https://patchwork.freedesktop.org/series/126546/
Matthew Brost (7):
drm/xe: Use a flags field instead of bools for VMA create
drm/xe: Use a flags field instead of bools for sync parse
drm/xe: Allow num_binds == 0 in VM bind IOCTL
drm/xe: Allow num_batch_buffer == 0 in exec IOCTL
drm/xe: Take in-syncs into account when num_execs or num_binds == 0
drm/xe: Add last fence as dependency for jobs on user exec queues
drm/xe/uapi: Uniform async vs sync handling
drivers/gpu/drm/xe/xe_exec.c | 88 +++++++--
drivers/gpu/drm/xe/xe_exec_queue.c | 12 +-
drivers/gpu/drm/xe/xe_exec_queue_types.h | 7 +-
drivers/gpu/drm/xe/xe_migrate.c | 14 +-
drivers/gpu/drm/xe/xe_sched_job.c | 17 ++
drivers/gpu/drm/xe/xe_sched_job.h | 4 +
drivers/gpu/drm/xe/xe_sync.c | 82 +++++++-
drivers/gpu/drm/xe/xe_sync.h | 11 +-
drivers/gpu/drm/xe/xe_vm.c | 242 ++++++++++++-----------
drivers/gpu/drm/xe/xe_vm_types.h | 15 +-
include/uapi/drm/xe_drm.h | 56 +++---
11 files changed, 373 insertions(+), 175 deletions(-)
--
2.34.1
next reply other threads:[~2023-12-07 5:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 5:57 Matthew Brost [this message]
2023-12-07 5:57 ` [Intel-xe] [RFC PATCH 1/7] drm/xe: Use a flags field instead of bools for VMA create Matthew Brost
2023-12-07 5:57 ` [Intel-xe] [RFC PATCH 2/7] drm/xe: Use a flags field instead of bools for sync parse Matthew Brost
2023-12-07 5:57 ` [Intel-xe] [RFC PATCH 3/7] drm/xe: Allow num_binds == 0 in VM bind IOCTL Matthew Brost
2023-12-07 5:57 ` [Intel-xe] [RFC PATCH 4/7] drm/xe: Allow num_batch_buffer == 0 in exec IOCTL Matthew Brost
2023-12-07 5:57 ` [Intel-xe] [RFC PATCH 5/7] drm/xe: Take in-syncs into account when num_execs or num_binds == 0 Matthew Brost
2023-12-08 15:04 ` Thomas Hellström
2023-12-12 17:18 ` Matthew Brost
2023-12-07 5:57 ` [Intel-xe] [RFC PATCH 6/7] drm/xe: Add last fence as dependency for jobs on user exec queues Matthew Brost
2023-12-07 5:57 ` [Intel-xe] [RFC PATCH 7/7] drm/xe/uapi: Uniform async vs sync handling Matthew Brost
2023-12-07 19:51 ` Rodrigo Vivi
2023-12-08 15:00 ` Thomas Hellström
2023-12-08 9:45 ` Matthew Brost
2023-12-11 15:43 ` Thomas Hellström
2023-12-11 16:49 ` Matthew Brost
2023-12-11 18:11 ` Thomas Hellström
2023-12-11 21:11 ` Matthew Brost
2023-12-12 8:43 ` Thomas Hellström
2023-12-08 12:24 ` Matthew Brost
2023-12-11 15:34 ` Thomas Hellström
2023-12-11 16:50 ` Matthew Brost
2023-12-07 7:38 ` [Intel-xe] ✗ CI.Patch_applied: 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=20231207055729.438642-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