All of lore.kernel.org
 help / color / mirror / Atom feed
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 0/4] drm/xe: Allow migrate vm gpu submissions from reclaim context
Date: Wed, 22 May 2024 13:17:47 +0200	[thread overview]
Message-ID: <20240522111751.80380-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.

However since 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.

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_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         |  12 +-
 drivers/gpu/drm/xe/xe_sched_job.c        | 152 +++++++++++++----------
 drivers/gpu/drm/xe/xe_sched_job_types.h  |  18 ++-
 drivers/gpu/drm/xe/xe_trace.h            |   2 +-
 11 files changed, 206 insertions(+), 119 deletions(-)

-- 
2.44.0


             reply	other threads:[~2024-05-22 11:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-22 11:17 Thomas Hellström [this message]
2024-05-22 11:17 ` [PATCH 1/4] drm/xe: Split lrc seqno fence creation up Thomas Hellström
2024-05-22 11:17 ` [PATCH 2/4] drm/xe: Don't initialize fences at xe_sched_job_create() Thomas Hellström
2024-05-22 11:17 ` [PATCH 3/4] drm/xe: Remove xe_lrc_create_seqno_fence() Thomas Hellström
2024-05-22 11:17 ` [PATCH 4/4] drm/xe: Move job creation out of the struct xe_migrate::job_mutex Thomas Hellström
2024-05-22 11:40 ` ✓ CI.Patch_applied: success for drm/xe: Allow migrate vm gpu submissions from reclaim context Patchwork
2024-05-22 11:40 ` ✗ CI.checkpatch: warning " Patchwork
2024-05-22 11:41 ` ✓ CI.KUnit: success " Patchwork
2024-05-22 11:53 ` ✓ CI.Build: " Patchwork
2024-05-22 11:56 ` ✓ CI.Hooks: " Patchwork
2024-05-22 11:57 ` ✓ CI.checksparse: " Patchwork
2024-05-22 13:06 ` ✗ CI.BAT: failure " Patchwork
2024-05-22 15:55 ` ✗ CI.FULL: " 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=20240522111751.80380-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.