All of 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>,
	"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: Fri, 12 Sep 2025 09:49:33 +0300	[thread overview]
Message-ID: <aMPCfRObHMg6DZAs@jlahtine-mobl> (raw)

Hi Dave & Sima,

Here's the final drm-intel-gt-next PR towards v6.18.

Debug improvement to include GuC registers in error state and
two smaller improvements.

Regards, Joonas

***

drm-intel-gt-next-2025-09-12:

Driver Changes:

- Include the GuC registers in the error state (Daniele)
- Use memdup_user() (Thorsten)
- Selftest improvements (Jonathan)

The following changes since commit b7a855f488c6825e3dc06e78c49326491bef6f98:

  drm/i915/gt: Relocate Gen6 context-specific workaround (2025-08-18 20:32:25 -0100)

are available in the Git repository at:

  https://gitlab.freedesktop.org/drm/i915/kernel.git tags/drm-intel-gt-next-2025-09-12

for you to fetch changes up to ba391a102ec11ab7f5b249e46dcf61ef836a57e7:

  drm/i915/guc: Include the GuC registers in the error state (2025-09-11 11:28:02 -0700)

----------------------------------------------------------------
Driver Changes:

- Include the GuC registers in the error state (Daniele)
- Use memdup_user() (Thorsten)
- Selftest improvements (Jonathan)

----------------------------------------------------------------
Daniele Ceraolo Spurio (1):
      drm/i915/guc: Include the GuC registers in the error state

Jonathan Cavitt (1):
      drm/i915/gt: Fix memory leak in hangcheck selftest

Thorsten Blum (1):
      drm/i915: Replace kmalloc() + copy_from_user() with memdup_user()

 drivers/gpu/drm/i915/gem/i915_gem_context.c  |  12 +---
 drivers/gpu/drm/i915/gt/selftest_hangcheck.c |   4 +-
 drivers/gpu/drm/i915/gt/uc/intel_guc_fw.c    |   8 +++
 drivers/gpu/drm/i915/gt/uc/intel_guc_reg.h   |   1 +
 drivers/gpu/drm/i915/i915_gpu_error.c        | 102 +++++++++++++++++++++++++++
 drivers/gpu/drm/i915/i915_gpu_error.h        |   1 +
 6 files changed, 116 insertions(+), 12 deletions(-)

             reply	other threads:[~2025-09-12  6:49 UTC|newest]

Thread overview: 85+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-12  6:49 Joonas Lahtinen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-05-29  9:31 [PULL] drm-intel-gt-next Joonas Lahtinen
2026-03-12  9:02 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-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
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-15 12:11 ` Joonas Lahtinen
2023-12-08 16:18 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=aMPCfRObHMg6DZAs@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=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 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.