From: Tvrtko Ursulin <tursulin@igalia.com>
To: Dave Airlie <airlied@gmail.com>, Simona Vetter <simona.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, 2 Jul 2025 08:44:16 +0100 [thread overview]
Message-ID: <aGTjUBeOQFw26bRT@linux> (raw)
Hi Dave, Sima,
Here comes the first pull request for 6.17.
Headline feature is that Ville was able to move DG1 out of force probe.
Other than that mostly fixes in the GuC backend.
One cross-merge to fix the build.
Regards,
Tvrtko
drm-intel-gt-next-2025-07-02:
Driver Changes:
Fixes/improvements/new stuff:
- Avoid GuC scheduling stalls [guc] (Julia Filipchuk)
- Remove force_probe requirement for DG1 (Ville Syrjälä)
- Handle errors correctly to avoid losing GuC-2-Host messages [guc] (Jesus Narvaez)
- Avoid double wakeref put if GuC context deregister failed [guc] (Jesus Narvaez)
- Avoid timeline memory leak with signals and legacy platforms [ringbuf] (Janusz Krzysztofik)
- Fix MEI (discrete) interrupt handler on RT kernels [gsc] (Junxiao Chang)
Miscellaneous:
- Allow larger memory allocation [selftest] (Mikolaj Wasiak)
- Use provided dma_fence_is_chain (Tvrtko Ursulin)
- Fix build error with GCOV and AutoFDO enabled [pmu] (Tzung-Bi Shih)
- Fix build error some more (Arnd Bergmann)
- Reduce stack usage in igt_vma_pin1() (Arnd Bergmann)
- Move out engine related macros from i915_drv.h (Krzysztof Karas)
- Move GEM_QUIRK_PIN_SWIZZLED_PAGES to i915_gem.h (Krzysztof Karas)
The following changes since commit f8bb3ed3197966fb60bedcbdc126d2bd5bc0a77f:
drm/nouveau/tegra: Fix error pointer vs NULL return in nvkm_device_tegra_resource_addr() (2025-05-24 14:36:07 +1000)
are available in the Git repository at:
https://gitlab.freedesktop.org/drm/i915/kernel.git tags/drm-intel-gt-next-2025-07-02
for you to fetch changes up to dccf655f69002d496a527ba441b4f008aa5bebbf:
drm/i915/gsc: mei interrupt top half should be in irq disabled context (2025-06-30 14:21:06 -0400)
----------------------------------------------------------------
Driver Changes:
Fixes/improvements/new stuff:
- Avoid GuC scheduling stalls [guc] (Julia Filipchuk)
- Remove force_probe requirement for DG1 (Ville Syrjälä)
- Handle errors correctly to avoid losing GuC-2-Host messages [guc] (Jesus Narvaez)
- Avoid double wakeref put if GuC context deregister failed [guc] (Jesus Narvaez)
- Avoid timeline memory leak with signals and legacy platforms [ringbuf] (Janusz Krzysztofik)
- Fix MEI (discrete) interrupt handler on RT kernels [gsc] (Junxiao Chang)
Miscellaneous:
- Allow larger memory allocation [selftest] (Mikolaj Wasiak)
- Use provided dma_fence_is_chain (Tvrtko Ursulin)
- Fix build error with GCOV and AutoFDO enabled [pmu] (Tzung-Bi Shih)
- Fix build error some more (Arnd Bergmann)
- Reduce stack usage in igt_vma_pin1() (Arnd Bergmann)
- Move out engine related macros from i915_drv.h (Krzysztof Karas)
- Move GEM_QUIRK_PIN_SWIZZLED_PAGES to i915_gem.h (Krzysztof Karas)
----------------------------------------------------------------
Arnd Bergmann (2):
drm/i915: fix build error some more
drm/i915: reduce stack usage in igt_vma_pin1()
Janusz Krzysztofik (1):
drm/i915/gt: Fix timeline left held on VMA alloc error
Jesus Narvaez (2):
drm/i915/guc: Check if expecting reply before decrementing outstanding_submission_g2h
drm/i915/guc: Handle race condition where wakeref count drops below 0
Joonas Lahtinen (2):
Revert "drm/i915/gem: Allow EXEC_CAPTURE on recoverable contexts on DG1"
Merge drm/drm-next into drm-intel-gt-next
Julia Filipchuk (1):
drm/i915/guc: Enable DUAL_QUEUE_WA for newer platforms
Junxiao Chang (1):
drm/i915/gsc: mei interrupt top half should be in irq disabled context
Krzysztof Karas (2):
drm/i915: Move out engine related macros from i915_drv.h
drm/i915: move GEM_QUIRK_PIN_SWIZZLED_PAGES to i915_gem.h
Mikolaj Wasiak (1):
drm/i915/selftest: allow larger memory allocation
Tvrtko Ursulin (1):
drm/i915: Use provided dma_fence_is_chain
Tzung-Bi Shih (1):
drm/i915/pmu: Fix build error with GCOV and AutoFDO enabled
Ville Syrjälä (2):
drm/i915/gem: Allow EXEC_CAPTURE on recoverable contexts on DG1
drm/i915/pci: Remove force_probe requirement for DG1
drivers/gpu/drm/i915/gem/i915_gem_wait.c | 7 +----
drivers/gpu/drm/i915/gt/intel_engine.h | 31 ++++++++++++++++++++
drivers/gpu/drm/i915/gt/intel_gsc.c | 2 +-
drivers/gpu/drm/i915/gt/intel_ring_submission.c | 3 +-
drivers/gpu/drm/i915/gt/uc/intel_guc.c | 7 ++++-
drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c | 19 ++++++++++---
drivers/gpu/drm/i915/i915_drv.h | 33 ----------------------
drivers/gpu/drm/i915/i915_gem.h | 2 ++
drivers/gpu/drm/i915/i915_pci.c | 1 -
drivers/gpu/drm/i915/i915_pmu.c | 6 ++--
drivers/gpu/drm/i915/i915_vma.c | 20 +++++++++++++
drivers/gpu/drm/i915/i915_vma.h | 22 ++-------------
.../gpu/drm/i915/selftests/intel_memory_region.c | 14 ++-------
13 files changed, 86 insertions(+), 81 deletions(-)
next reply other threads:[~2025-07-02 7:44 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 7:44 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-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-06-12 12:57 Tvrtko Ursulin
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=aGTjUBeOQFw26bRT@linux \
--to=tursulin@igalia.com \
--cc=airlied@gmail.com \
--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=simona.vetter@ffwll.ch \
--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).