Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Joonas Lahtinen <joonas.lahtinen@linux.intel.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>,
	"Matthew Brost" <matthew.brost@intel.com>,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	"Oded Gabbay" <ogabbay@kernel.org>,
	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: Fri, 29 May 2026 12:31:01 +0300	[thread overview]
Message-ID: <ahlc1R5bzJvmBLlZ@jlahtine-mobl> (raw)

Hi Dave & Sima,

Here goes the singular drm-intel-gt-next PR towards 7.2.

Fix for more robust fence handling after reset on SNB. A couple
UAF/underflow fixes. Selftest improvements and then cleaning up
EXECBUF logic to avoid false positives from AI scanners.

Note that there is a drm-next backmerge to pull in a patch from
mainline tree to revert.

Best Regards, Joonas

***

drm-intel-gt-next-2026-05-29:

Cross-subsystem Changes:

- Backmerge of drm-next to pull in a commit to revert

Driver Changes:

- Avoid skipping already signaled fence after reset (Sebastian)
- Fix potential UAF in TTM object purge (Janusz)
- Fix refcount underflow in intel_engine_park_heartbeat (Sebastian)

- Drop check for changed VM in EXECBUF (Joonas)
- Revert the "else vma = NULL" patch for being superseded (Joonas)
- Selfest improvements (Janusz, Krzysztof)

The following changes since commit f96538285cfdbb3acf5e3356e0bb88c38815790b:

  Merge tag 'drm-misc-next-2026-05-07' of https://gitlab.freedesktop.org/drm/misc/kernel into drm-next (2026-05-08 14:16:04 +1000)

are available in the Git repository at:

  https://gitlab.freedesktop.org/drm/i915/kernel.git tags/drm-intel-gt-next-2026-05-29

for you to fetch changes up to 6c064db893f548d57036fce17c6493808396e620:

  Revert "i915: don't use a vma that didn't match the context VM" (2026-05-20 10:46:41 +0300)

----------------------------------------------------------------
Cross-subsystem Changes:

- Backmerge of drm-next to pull in a commit to revert

Driver Changes:

- Avoid skipping already signaled fence after reset (Sebastian)
- Fix potential UAF in TTM object purge (Janusz)
- Fix refcount underflow in intel_engine_park_heartbeat (Sebastian)

- Drop check for changed VM in EXECBUF (Joonas)
- Revert the "else vma = NULL" patch for being superseded (Joonas)
- Selfest improvements (Janusz, Krzysztof)

----------------------------------------------------------------
Janusz Krzysztofik (2):
      drm/i915: Skip deprecated selftest
      drm/i915: Fix potential UAF in TTM object purge

Joonas Lahtinen (3):
      drm/i915/gem: Drop check for changed VM in EXECBUF
      Merge drm/drm-next into drm-intel-gt-next
      Revert "i915: don't use a vma that didn't match the context VM"

Krzysztof Karas (2):
      drm/i915/selftests: Prevent userspace mapping invalidation
      drm/i915/selftests: Run vma tests only if current->mm is present

Sebastian Brzezinka (2):
      drm/i915/gt: fix refcount underflow in intel_engine_park_heartbeat
      drm/i915: skip __i915_request_skip() for already signaled requests

 drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c     |  2 -
 drivers/gpu/drm/i915/gem/i915_gem_ttm.c            | 28 ++++----
 drivers/gpu/drm/i915/gem/selftests/i915_gem_mman.c | 16 ++---
 drivers/gpu/drm/i915/gt/intel_reset.c              |  3 +-
 drivers/gpu/drm/i915/gt/selftest_workarounds.c     |  3 +
 drivers/gpu/drm/i915/i915_selftest.h               |  1 +
 drivers/gpu/drm/i915/selftests/i915_selftest.c     | 74 +++++++++++++++++++++-
 7 files changed, 103 insertions(+), 24 deletions(-)

             reply	other threads:[~2026-05-29  9:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-29  9:31 Joonas Lahtinen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-03-12  9:02 [PULL] drm-intel-gt-next Tvrtko Ursulin
2026-01-16  8:13 Joonas Lahtinen
2025-11-14 16:22 Tvrtko Ursulin
2025-10-29 11:43 Tvrtko Ursulin
2025-10-31 21:02 ` Simona Vetter
2025-09-12  6:49 Joonas Lahtinen
2025-09-01 13:03 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-06-12 12:57 Tvrtko Ursulin
2024-04-26  7:17 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=ahlc1R5bzJvmBLlZ@jlahtine-mobl \
    --to=joonas.lahtinen@linux.intel.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=maarten.lankhorst@linux.intel.com \
    --cc=matthew.brost@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