From: Nirmoy Das <nirmoy.das@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: andi.shyti@intel.com, chris.p.wilson@linux.intel.com,
matthew.d.roper@intel.com, Nirmoy Das <nirmoy.das@intel.com>
Subject: [Intel-gfx] [PATCH 0/7] Update GGTT with MI_UPDATE_GTT on MTL
Date: Tue, 26 Sep 2023 10:37:35 +0200 [thread overview]
Message-ID: <20230926083742.14740-1-nirmoy.das@intel.com> (raw)
Implement a way to update GGTT using MI_UPDATE_GTT command
when possible for MTL as a suggested work around for HW bugs,
Wa_13010847436 and Wa_14019519902.
1st patch improve pm wakeref handeling which needed as we
do GGTT update with vm->mutext held and not allowed to alloc
memory.
2: Fix lockdep warning related to GT wakeref vs
blitter engine wakeref.
v3: Rearrange patches/diffs to fix code mixups(Andi)
v4: fix ce leak(Oak)
v5: rebase & resend with new "Test-with"
v6: move context ready status chnages to lower levels from
i915_driver.c. Add more docs and improve function names.
Chris Wilson (1):
drm/i915: Lift runtime-pm acquire callbacks out of intel_wakeref.mutex
Nirmoy Das (6):
drm/i915: Create a kernel context for GGTT updates
drm/i915: Implement for_each_sgt_daddr_next
drm/i915: Parameterize binder context creation
drm/i915: Implement GGTT update method with MI_UPDATE_GTT
drm/i915: Toggle binder context ready status
drm/i915: Enable GGTT updates with binder in MTL
drivers/gpu/drm/i915/gt/intel_engine.h | 2 +
drivers/gpu/drm/i915/gt/intel_engine_cs.c | 40 +++-
drivers/gpu/drm/i915/gt/intel_engine_types.h | 3 +
drivers/gpu/drm/i915/gt/intel_ggtt.c | 235 +++++++++++++++++++
drivers/gpu/drm/i915/gt/intel_gt.c | 49 ++++
drivers/gpu/drm/i915/gt/intel_gt.h | 3 +
drivers/gpu/drm/i915/gt/intel_gt_pm.c | 4 +
drivers/gpu/drm/i915/gt/intel_gtt.c | 5 +
drivers/gpu/drm/i915/gt/intel_gtt.h | 5 +
drivers/gpu/drm/i915/i915_scatterlist.h | 10 +
drivers/gpu/drm/i915/intel_wakeref.c | 52 ++--
11 files changed, 380 insertions(+), 28 deletions(-)
--
2.41.0
next reply other threads:[~2023-09-26 8:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 8:37 Nirmoy Das [this message]
2023-09-26 8:37 ` [Intel-gfx] [PATCH v2 1/7] drm/i915: Lift runtime-pm acquire callbacks out of intel_wakeref.mutex Nirmoy Das
2023-09-26 8:37 ` [Intel-gfx] [PATCH v3 2/7] drm/i915: Create a kernel context for GGTT updates Nirmoy Das
2023-09-26 8:37 ` [Intel-gfx] [PATCH 3/7] drm/i915: Implement for_each_sgt_daddr_next Nirmoy Das
2023-09-26 8:37 ` [Intel-gfx] [PATCH 4/7] drm/i915: Parameterize binder context creation Nirmoy Das
2023-09-26 8:37 ` [Intel-gfx] [PATCH v2 5/7] drm/i915: Implement GGTT update method with MI_UPDATE_GTT Nirmoy Das
2023-09-26 8:37 ` [Intel-gfx] [PATCH v2 6/7] drm/i915: Toggle binder context ready status Nirmoy Das
2023-09-26 8:37 ` [Intel-gfx] [PATCH 7/7] drm/i915: Enable GGTT updates with binder in MTL Nirmoy Das
2023-09-26 16:00 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Update GGTT with MI_UPDATE_GTT on MTL (rev10) Patchwork
2023-09-26 16:00 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-09-26 16:13 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-09-26 21:35 ` [Intel-gfx] [PATCH 0/7] Update GGTT with MI_UPDATE_GTT on MTL Andi Shyti
2023-09-27 3:20 ` [Intel-gfx] ✓ Fi.CI.IGT: success for Update GGTT with MI_UPDATE_GTT on MTL (rev10) Patchwork
2023-09-29 13:49 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Update GGTT with MI_UPDATE_GTT on MTL (rev11) Patchwork
2023-09-29 13:49 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-09-29 14:03 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-09-29 20:10 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-10-01 1:51 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for Update GGTT with MI_UPDATE_GTT on MTL (rev12) Patchwork
-- strict thread matches above, loose matches on Subject: below --
2023-09-18 17:02 [Intel-gfx] [PATCH 0/7] Update GGTT with MI_UPDATE_GTT on MTL Nirmoy Das
2023-09-15 8:34 Nirmoy Das
2023-09-13 13:09 Nirmoy Das
2023-09-13 13:09 ` Nirmoy Das
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=20230926083742.14740-1-nirmoy.das@intel.com \
--to=nirmoy.das@intel.com \
--cc=andi.shyti@intel.com \
--cc=chris.p.wilson@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.d.roper@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.