From: Tvrtko Ursulin <tursulin@igalia.com>
To: Dave Airlie <airlied@gmail.com>, Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: "Jani Nikula" <jani.nikula@linux.intel.com>,
"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
"Tvrtko Ursulin" <tursulin@ursulin.net>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Oded Gabbay" <ogabbay@kernel.org>,
"Lucas De Marchi" <lucas.demarchi@intel.com>,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
intel-xe@lists.freedesktop.org, dim-tools@lists.freedesktop.org
Subject: [PULL] drm-intel-gt-next
Date: Wed, 12 Jun 2024 12:57:06 +0000 [thread overview]
Message-ID: <Zmmazub+U9ewH9ts@linux> (raw)
Hi Dave, Sima,
Here is the main pull request for drm-intel-gt-next targeting 6.11.
First is the new userspace API for allowing upload of custom context
state used for replaying GPU hang error state captures. This will be
used by Mesa (see
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27594) for
debugging GPU hangs captured in the wild on real hardware. So far that
was only possible under simulation and that via some hacks. Also,
simulation in general has certain limitations to what hangs it can
reproduce. As the UAPI it is intended for Mesa developers only, it is
hidden behind a kconfig and runtime enablement switches.
Then there are fixes for hangs on Meteorlake due incorrect reduced CCS
configuration and a missing video engine workaround. Then fixes for a
couple race conditions in multi GT and breadcrumb handling, and a more
robust functional level reset by extending the timeout used.
A couple tiny cleanups here and there and finally one back-merge which
was required to land some display code base refactoring.
Regards,
Tvrtko
drm-intel-gt-next-2024-06-12:
UAPI Changes:
- Support replaying GPU hangs with captured context image (Tvrtko Ursulin)
Driver Changes:
Fixes/improvements/new stuff:
- Automate CCS Mode setting during engine resets [gt] (Andi Shyti)
- Revert "drm/i915: Remove extra multi-gt pm-references" (Janusz Krzysztofik)
- Fix HAS_REGION() usage in intel_gt_probe_lmem() (Ville Syrjälä)
- Disarm breadcrumbs if engines are already idle [gt] (Chris Wilson)
- Shadow default engine context image in the context (Tvrtko Ursulin)
- Support replaying GPU hangs with captured context image (Tvrtko Ursulin)
- avoid FIELD_PREP warning [guc] (Arnd Bergmann)
- Fix CCS id's calculation for CCS mode setting [gt] (Andi Shyti)
- Increase FLR timeout from 3s to 9s (Andi Shyti)
- Update workaround 14018575942 [mtl] (Angus Chen)
Future platform enablement:
- Enable w/a 16021333562 for DG2, MTL and ARL [guc] (John Harrison)
Miscellaneous:
- Pass the region ID rather than a bitmask to HAS_REGION() (Ville Syrjälä)
- Remove counter productive REGION_* wrappers (Ville Syrjälä)
- Fix typo [gem/i915_gem_ttm_move] (Deming Wang)
- Delete the live_hearbeat_fast selftest [gt] (Krzysztof Niemiec)
The following changes since commit 431c590c3ab0469dfedad3a832fe73556396ee52:
drm/tests: Add a unit test for range bias allocation (2024-05-16 12:50:14 +1000)
are available in the Git repository at:
https://gitlab.freedesktop.org/drm/i915/kernel.git tags/drm-intel-gt-next-2024-06-12
for you to fetch changes up to 79655e867ad6dfde2734c67c7704c0dd5bf1e777:
drm/i915/mtl: Update workaround 14018575942 (2024-06-11 16:06:20 +0200)
----------------------------------------------------------------
UAPI Changes:
- Support replaying GPU hangs with captured context image (Tvrtko Ursulin)
Driver Changes:
Fixes/improvements/new stuff:
- Automate CCS Mode setting during engine resets [gt] (Andi Shyti)
- Revert "drm/i915: Remove extra multi-gt pm-references" (Janusz Krzysztofik)
- Fix HAS_REGION() usage in intel_gt_probe_lmem() (Ville Syrjälä)
- Disarm breadcrumbs if engines are already idle [gt] (Chris Wilson)
- Shadow default engine context image in the context (Tvrtko Ursulin)
- Support replaying GPU hangs with captured context image (Tvrtko Ursulin)
- avoid FIELD_PREP warning [guc] (Arnd Bergmann)
- Fix CCS id's calculation for CCS mode setting [gt] (Andi Shyti)
- Increase FLR timeout from 3s to 9s (Andi Shyti)
- Update workaround 14018575942 [mtl] (Angus Chen)
Future platform enablement:
- Enable w/a 16021333562 for DG2, MTL and ARL [guc] (John Harrison)
Miscellaneous:
- Pass the region ID rather than a bitmask to HAS_REGION() (Ville Syrjälä)
- Remove counter productive REGION_* wrappers (Ville Syrjälä)
- Fix typo [gem/i915_gem_ttm_move] (Deming Wang)
- Delete the live_hearbeat_fast selftest [gt] (Krzysztof Niemiec)
----------------------------------------------------------------
Andi Shyti (3):
drm/i915/gt: Automate CCS Mode setting during engine resets
drm/i915/gt: Fix CCS id's calculation for CCS mode setting
drm/i915: Increase FLR timeout from 3s to 9s
Angus Chen (1):
drm/i915/mtl: Update workaround 14018575942
Arnd Bergmann (1):
drm/i915/guc: avoid FIELD_PREP warning
Chris Wilson (1):
drm/i915/gt: Disarm breadcrumbs if engines are already idle
Deming Wang (1):
drm/i915/gem/i915_gem_ttm_move: Fix typo
Janusz Krzysztofik (1):
Revert "drm/i915: Remove extra multi-gt pm-references"
John Harrison (1):
drm/i915/guc: Enable w/a 16021333562 for DG2, MTL and ARL
Niemiec, Krzysztof (1):
drm/i915/gt: Delete the live_hearbeat_fast selftest
Tvrtko Ursulin (3):
Merge drm/drm-next into drm-intel-gt-next
drm/i915: Shadow default engine context image in the context
drm/i915: Support replaying GPU hangs with captured context image
Ville Syrjälä (3):
drm/i915: Fix HAS_REGION() usage in intel_gt_probe_lmem()
drm/i915: Pass the region ID rather than a bitmask to HAS_REGION()
drm/i915: Remove counter productive REGION_* wrappers
drivers/gpu/drm/i915/Kconfig.debug | 17 ++++
drivers/gpu/drm/i915/gem/i915_gem_context.c | 113 +++++++++++++++++++++
drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c | 18 ++++
drivers/gpu/drm/i915/gem/i915_gem_ttm_move.c | 2 +-
drivers/gpu/drm/i915/gt/intel_breadcrumbs.c | 15 ++-
drivers/gpu/drm/i915/gt/intel_context.c | 2 +
drivers/gpu/drm/i915/gt/intel_context.h | 22 ++++
drivers/gpu/drm/i915/gt/intel_context_types.h | 3 +
drivers/gpu/drm/i915/gt/intel_engine_cs.c | 6 ++
drivers/gpu/drm/i915/gt/intel_gt_ccs_mode.c | 8 +-
drivers/gpu/drm/i915/gt/intel_gt_ccs_mode.h | 2 +-
drivers/gpu/drm/i915/gt/intel_gt_types.h | 8 ++
drivers/gpu/drm/i915/gt/intel_lrc.c | 8 +-
drivers/gpu/drm/i915/gt/intel_ring_submission.c | 8 +-
drivers/gpu/drm/i915/gt/intel_workarounds.c | 12 ++-
.../gpu/drm/i915/gt/selftest_engine_heartbeat.c | 110 --------------------
drivers/gpu/drm/i915/gt/uc/abi/guc_klvs_abi.h | 7 +-
drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c | 32 +++---
drivers/gpu/drm/i915/i915_drv.h | 4 +-
drivers/gpu/drm/i915/i915_params.c | 5 +
drivers/gpu/drm/i915/i915_params.h | 3 +-
drivers/gpu/drm/i915/i915_pci.c | 6 +-
drivers/gpu/drm/i915/intel_memory_region.c | 2 +-
drivers/gpu/drm/i915/intel_memory_region.h | 5 -
drivers/gpu/drm/i915/intel_uncore.c | 9 +-
drivers/gpu/drm/i915/selftests/mock_gem_device.c | 2 +-
include/uapi/drm/i915_drm.h | 27 +++++
27 files changed, 296 insertions(+), 160 deletions(-)
next reply other threads:[~2024-06-12 12:57 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 12:57 Tvrtko Ursulin [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-09-01 13:03 [PULL] drm-intel-gt-next Joonas Lahtinen
2025-07-02 7:44 Tvrtko Ursulin
2025-05-08 6:21 Joonas Lahtinen
2025-03-12 23:24 Tvrtko Ursulin
2025-02-26 8:13 Tvrtko Ursulin
2025-01-10 9:03 Joonas Lahtinen
2024-12-18 9:48 Joonas Lahtinen
2024-10-23 9:16 Tvrtko Ursulin
2024-09-06 10:55 Joonas Lahtinen
2024-08-23 9:55 Joonas Lahtinen
2024-08-27 10:59 ` Daniel Vetter
2024-07-04 7:31 Tvrtko Ursulin
2024-07-05 10:15 ` Daniel Vetter
2024-04-26 7:17 Joonas Lahtinen
2024-02-28 14:02 Tvrtko Ursulin
2024-02-15 10:06 Tvrtko Ursulin
2024-02-16 2:58 ` Dave Airlie
2024-02-16 9:31 ` Thomas Hellström
2024-02-16 9:33 ` Thomas Hellström
2024-02-16 9:41 ` Joonas Lahtinen
2024-02-20 15:14 ` Joonas Lahtinen
2023-12-15 12:11 Joonas Lahtinen
2023-12-08 16:18 Joonas Lahtinen
2023-10-19 14:54 Tvrtko Ursulin
2023-10-12 10:30 Tvrtko Ursulin
2023-09-28 12:36 Tvrtko Ursulin
2023-08-11 10:47 Joonas Lahtinen
2023-08-04 8:45 Joonas Lahtinen
2023-06-08 15:34 Tvrtko Ursulin
2023-05-24 18:09 Tvrtko Ursulin
2023-04-06 11:41 Maarten Lankhorst
2023-04-06 12:34 ` Jani Nikula
2023-04-06 13:00 ` Daniel Vetter
2023-04-06 8:18 Joonas Lahtinen
2023-04-06 12:38 ` Daniel Vetter
2023-03-16 12:58 Joonas Lahtinen
2023-02-01 11:36 Tvrtko Ursulin
2023-01-18 11:24 Tvrtko Ursulin
2023-01-24 15:32 ` Daniel Vetter
2022-11-18 9:12 Joonas Lahtinen
2022-11-03 8:03 Joonas Lahtinen
2022-10-31 11:07 Joonas Lahtinen
2022-11-01 19:33 ` Dave Airlie
2022-09-16 8:47 Joonas Lahtinen
2022-09-09 11:20 Joonas Lahtinen
2022-08-24 12:01 Joonas Lahtinen
2022-07-13 21:31 Rodrigo Vivi
2022-07-21 15:06 ` Vivi, Rodrigo
2022-06-29 10:45 Tvrtko Ursulin
2022-05-05 6:39 Tvrtko Ursulin
2022-04-27 10:49 Tvrtko Ursulin
2022-03-03 7:50 Joonas Lahtinen
2022-02-17 10:26 Joonas Lahtinen
2022-02-20 23:30 ` Dave Airlie
2022-02-21 9:21 ` Jani Nikula
2022-02-22 19:44 ` Lucas De Marchi
2022-02-23 20:35 ` Vivi, Rodrigo
2021-12-23 12:47 Tvrtko Ursulin
2021-12-09 13:14 Tvrtko Ursulin
2021-10-21 13:07 Joonas Lahtinen
2021-10-08 9:27 Joonas Lahtinen
2021-08-06 10:06 Joonas Lahtinen
2021-08-06 10:10 ` Joonas Lahtinen
2021-06-10 9:40 Joonas Lahtinen
2021-05-28 7:25 Joonas Lahtinen
2021-05-28 7:27 ` Joonas Lahtinen
2021-06-02 0:28 ` Dave Airlie
2021-06-02 4:17 ` Dave Airlie
2021-06-02 4:30 ` Dave Airlie
2021-04-06 13:40 Joonas Lahtinen
2021-01-21 15:07 Joonas Lahtinen
2021-01-14 15:22 Joonas Lahtinen
2020-11-12 16:34 Joonas Lahtinen
2020-09-07 13:00 Joonas Lahtinen
2020-09-04 13:39 Joonas Lahtinen
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=Zmmazub+U9ewH9ts@linux \
--to=tursulin@igalia.com \
--cc=airlied@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dim-tools@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=lucas.demarchi@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=ogabbay@kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=thomas.hellstrom@linux.intel.com \
--cc=tursulin@ursulin.net \
--cc=tzimmermann@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).