From: Matthew Brost <matthew.brost@intel.com>
To: <intel-xe@lists.freedesktop.org>
Subject: [Intel-xe] [PATCH 0/8] Scheduler changes for upstreaming
Date: Sun, 21 May 2023 18:50:32 -0700 [thread overview]
Message-ID: <20230522015040.3849776-1-matthew.brost@intel.com> (raw)
First 8 patches of the follow series /w comments addressed:
https://patchwork.freedesktop.org/series/117156/
A follow up with submit a GuC doorbell series and a GPUVA series.
Matthew Brost (8):
fixup! drm/sched: Convert drm scheduler to use a work queue rather
than kthread
drm/sched: Move schedule policy to scheduler
drm/sched: Add DRM_SCHED_POLICY_SINGLE_ENTITY scheduling policy
drm/xe: Use DRM_SCHED_POLICY_SINGLE_ENTITY mode
drm/xe: Long running job update
drm/xe: Ensure LR engines are not persistent
drm/xe: Only try to lock external BOs in VM bind
drm/xe: VM LRU bulk move
drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 3 +-
drivers/gpu/drm/etnaviv/etnaviv_sched.c | 5 +-
drivers/gpu/drm/lima/lima_sched.c | 5 +-
drivers/gpu/drm/msm/msm_ringbuffer.c | 5 +-
drivers/gpu/drm/panfrost/panfrost_job.c | 5 +-
drivers/gpu/drm/scheduler/sched_entity.c | 62 +++++++++++---
drivers/gpu/drm/scheduler/sched_fence.c | 2 +-
drivers/gpu/drm/scheduler/sched_main.c | 88 ++++++++++++++++---
drivers/gpu/drm/v3d/v3d_sched.c | 25 +++---
drivers/gpu/drm/xe/xe_bo.c | 32 ++++++-
drivers/gpu/drm/xe/xe_bo.h | 4 +-
drivers/gpu/drm/xe/xe_devcoredump_types.h | 1 +
drivers/gpu/drm/xe/xe_dma_buf.c | 2 +-
drivers/gpu/drm/xe/xe_engine.c | 36 +++++++-
drivers/gpu/drm/xe/xe_engine.h | 4 +
drivers/gpu/drm/xe/xe_exec.c | 14 +++
drivers/gpu/drm/xe/xe_execlist.c | 3 +-
drivers/gpu/drm/xe/xe_guc_engine_types.h | 2 +
drivers/gpu/drm/xe/xe_guc_submit.c | 99 +++++++++++++++++++---
drivers/gpu/drm/xe/xe_trace.h | 5 ++
drivers/gpu/drm/xe/xe_vm.c | 12 ++-
drivers/gpu/drm/xe/xe_vm_types.h | 3 +
include/drm/gpu_scheduler.h | 29 +++++--
23 files changed, 371 insertions(+), 75 deletions(-)
--
2.34.1
next reply other threads:[~2023-05-22 1:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 1:50 Matthew Brost [this message]
2023-05-22 1:50 ` [Intel-xe] [PATCH 1/8] fixup! drm/sched: Convert drm scheduler to use a work queue rather than kthread Matthew Brost
2023-05-22 14:44 ` Rodrigo Vivi
2023-05-22 1:50 ` [Intel-xe] [PATCH 2/8] drm/sched: Move schedule policy to scheduler Matthew Brost
2023-05-22 1:50 ` [Intel-xe] [PATCH 3/8] drm/sched: Add DRM_SCHED_POLICY_SINGLE_ENTITY scheduling policy Matthew Brost
2023-05-22 5:48 ` Christopher Snowhill
2023-05-23 5:49 ` Matthew Brost
2023-05-22 6:52 ` Christopher Snowhill
2023-05-22 7:52 ` Christopher Snowhill
2023-05-22 1:50 ` [Intel-xe] [PATCH 4/8] drm/xe: Use DRM_SCHED_POLICY_SINGLE_ENTITY mode Matthew Brost
2023-05-22 1:50 ` [Intel-xe] [PATCH 5/8] drm/xe: Long running job update Matthew Brost
2023-05-22 1:50 ` [Intel-xe] [PATCH 6/8] drm/xe: Ensure LR engines are not persistent Matthew Brost
2023-05-22 1:50 ` [Intel-xe] [PATCH 7/8] drm/xe: Only try to lock external BOs in VM bind Matthew Brost
2023-05-22 1:50 ` [Intel-xe] [PATCH 8/8] drm/xe: VM LRU bulk move Matthew Brost
2023-05-22 1:52 ` [Intel-xe] ✓ CI.Patch_applied: success for Scheduler changes for upstreaming Patchwork
2023-05-22 1:54 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-05-22 1:58 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-05-22 4:39 ` [Intel-xe] [PATCH 0/8] " Christopher Snowhill
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=20230522015040.3849776-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