From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: intel-xe@lists.freedesktop.org
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Matthew Brost" <matthew.brost@intel.com>
Subject: [PATCH v3 0/5] drm/xe: Allow migrate vm gpu submissions from reclaim context
Date: Fri, 24 May 2024 09:19:35 +0200 [thread overview]
Message-ID: <20240524071940.83042-1-thomas.hellstrom@linux.intel.com> (raw)
On lunar lake, we need to be able to copy CCS compression metadata from
reclaim context when using a shrinker.
ince we do dma_fence allocations under the
struct xe_migrate::job_mutex, we're facing a lockdep violation.
This patchset deals with moving the job + fence allocation out of
the job_mutex by splitting up the fence allocation- and
initialization.
v2:
- Add a patch from Matthew Brost to fix up the use of
composite fence seqno.
- A couple of bugfixes as detailed in patch 3.
v3:
- Rebase on drm-tip.
Matthew Brost (1):
drm/xe: Decouple job seqno and lrc seqno
Thomas Hellström (4):
drm/xe: Split lrc seqno fence creation up
drm/xe: Don't initialize fences at xe_sched_job_create()
drm/xe: Remove xe_lrc_create_seqno_fence()
drm/xe: Move job creation out of the struct xe_migrate::job_mutex
drivers/gpu/drm/xe/xe_exec_queue.c | 5 -
drivers/gpu/drm/xe/xe_exec_queue_types.h | 10 --
drivers/gpu/drm/xe/xe_guc_submit.c | 5 +-
drivers/gpu/drm/xe/xe_hw_fence.c | 59 ++++++--
drivers/gpu/drm/xe/xe_hw_fence.h | 7 +-
drivers/gpu/drm/xe/xe_lrc.c | 39 +++++-
drivers/gpu/drm/xe/xe_lrc.h | 4 +-
drivers/gpu/drm/xe/xe_migrate.c | 17 ++-
drivers/gpu/drm/xe/xe_ring_ops.c | 22 +--
drivers/gpu/drm/xe/xe_sched_job.c | 165 +++++++++++++----------
drivers/gpu/drm/xe/xe_sched_job.h | 5 +
drivers/gpu/drm/xe/xe_sched_job_types.h | 20 ++-
drivers/gpu/drm/xe/xe_trace.h | 9 +-
13 files changed, 235 insertions(+), 132 deletions(-)
--
2.44.0
next reply other threads:[~2024-05-24 7:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 7:19 Thomas Hellström [this message]
2024-05-24 7:19 ` [PATCH v3 1/5] drm/xe: Decouple job seqno and lrc seqno Thomas Hellström
2024-05-24 12:26 ` Rodrigo Vivi
2024-05-24 12:56 ` Thomas Hellström
2024-05-24 19:44 ` Rodrigo Vivi
2024-05-24 7:19 ` [PATCH v3 2/5] drm/xe: Split lrc seqno fence creation up Thomas Hellström
2024-05-24 12:32 ` Rodrigo Vivi
2024-05-24 7:19 ` [PATCH v3 3/5] drm/xe: Don't initialize fences at xe_sched_job_create() Thomas Hellström
2024-05-24 13:12 ` Rodrigo Vivi
2024-05-24 13:22 ` Thomas Hellström
2024-05-24 19:45 ` Rodrigo Vivi
2024-05-24 7:19 ` [PATCH v3 4/5] drm/xe: Remove xe_lrc_create_seqno_fence() Thomas Hellström
2024-05-24 12:33 ` Rodrigo Vivi
2024-05-24 7:19 ` [PATCH v3 5/5] drm/xe: Move job creation out of the struct xe_migrate::job_mutex Thomas Hellström
2024-05-24 13:14 ` Rodrigo Vivi
2024-05-24 8:18 ` ✓ CI.Patch_applied: success for drm/xe: Allow migrate vm gpu submissions from reclaim context (rev3) Patchwork
2024-05-24 8:18 ` ✓ CI.checkpatch: " Patchwork
2024-05-24 8:19 ` ✓ CI.KUnit: " Patchwork
2024-05-24 8:31 ` ✓ CI.Build: " Patchwork
2024-05-24 8:33 ` ✓ CI.Hooks: " Patchwork
2024-05-24 8:35 ` ✓ CI.checksparse: " Patchwork
2024-05-24 9:05 ` ✓ CI.BAT: " Patchwork
2024-05-24 10:48 ` ✗ 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=20240524071940.83042-1-thomas.hellstrom@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.