All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Hellstrom <thomas.hellstrom@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>,
	"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-xe-fixes
Date: Thu, 12 Dec 2024 20:28:58 +0100	[thread overview]
Message-ID: <Z1s5elHXOyeIHnE0@fedora> (raw)

Dave, Simona

This week'd drm-xe-fixes PR.

Thanks,
Thomas

drm-xe-fixes-2024-12-12:
- Fix a KUNIT test error message (Mirsad Todorovac)
- Fix an invalidation fence PM ref leak (Daniele)
- Fix a register pool UAF (Lucas)
The following changes since commit 5dce85fecb87751ec94526e1ac516dd7871e2e0c:

  drm/xe: Move the coredump registration to the worker thread (2024-12-03 10:33:13 +0100)

are available in the Git repository at:

  https://gitlab.freedesktop.org/drm/xe/kernel.git tags/drm-xe-fixes-2024-12-12

for you to fetch changes up to d7b028656c29b22fcde1c6ee1df5b28fbba987b5:

  drm/xe/reg_sr: Remove register pool (2024-12-12 16:57:28 +0100)

----------------------------------------------------------------
- Fix a KUNIT test error message (Mirsad Todorovac)
- Fix an invalidation fence PM ref leak (Daniele)
- Fix a register pool UAF (Lucas)

----------------------------------------------------------------
Daniele Ceraolo Spurio (1):
      drm/xe: Call invalidation_fence_fini for PT inval fences in error state

Lucas De Marchi (1):
      drm/xe/reg_sr: Remove register pool

Mirsad Todorovac (1):
      drm/xe: fix the ERR_PTR() returned on failure to allocate tiny pt

 drivers/gpu/drm/xe/tests/xe_migrate.c       |  4 ++--
 drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c |  8 ++++++++
 drivers/gpu/drm/xe/xe_gt_tlb_invalidation.h |  1 +
 drivers/gpu/drm/xe/xe_pt.c                  |  3 +--
 drivers/gpu/drm/xe/xe_reg_sr.c              | 31 ++++++-----------------------
 drivers/gpu/drm/xe/xe_reg_sr_types.h        |  6 ------
 6 files changed, 18 insertions(+), 35 deletions(-)

             reply	other threads:[~2024-12-12 19:29 UTC|newest]

Thread overview: 96+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-12 19:28 Thomas Hellstrom [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-05-14 14:05 [PULL] drm-xe-fixes Rodrigo Vivi
2026-05-07  7:04 Matthew Brost
2026-04-30 20:00 Rodrigo Vivi
2026-04-08 20:01 Rodrigo Vivi
2026-04-02 12:50 Rodrigo Vivi
2026-03-26 12:03 Rodrigo Vivi
2026-03-19 21:00 Thomas Hellstrom
2026-03-05 13:35 Rodrigo Vivi
2026-02-26 13:09 Rodrigo Vivi
2026-02-05 15:26 Thomas Hellstrom
2026-01-29 20:12 Thomas Hellstrom
2026-01-22 12:52 Thomas Hellstrom
2025-12-30  8:56 Thomas Hellstrom
2025-12-18 23:21 Thomas Hellstrom
2025-11-28  0:24 Lucas De Marchi
2025-11-21  6:19 Lucas De Marchi
2025-11-13 19:07 Lucas De Marchi
2025-11-07 15:07 Lucas De Marchi
2025-10-30 20:44 Lucas De Marchi
2025-10-31 18:13 ` Simona Vetter
2025-10-24  3:59 Lucas De Marchi
2025-10-24 11:42 ` Simona Vetter
2025-10-16 16:26 Lucas De Marchi
2025-09-25 13:05 Rodrigo Vivi
2025-09-18 13:41 Rodrigo Vivi
2025-09-11 15:29 Rodrigo Vivi
2025-09-11 15:31 ` Vivi, Rodrigo
2025-09-03 18:58 Rodrigo Vivi
2025-08-27 15:46 Rodrigo Vivi
2025-08-21 19:20 Rodrigo Vivi
2025-08-14 16:17 Rodrigo Vivi
2025-07-24 20:22 Thomas Hellstrom
2025-07-18  3:31 Lucas De Marchi
2025-07-11  5:17 Lucas De Marchi
2025-07-03 23:24 Lucas De Marchi
2025-06-26 14:06 Thomas Hellstrom
2025-06-19 16:03 Thomas Hellstrom
2025-06-12 16:33 Thomas Hellstrom
2025-05-23  5:47 Lucas De Marchi
2025-05-15 15:04 Lucas De Marchi
2025-05-09  5:12 Lucas De Marchi
2025-05-02  3:23 Lucas De Marchi
2025-04-18  5:43 Lucas De Marchi
2025-04-10 21:06 Lucas De Marchi
2025-03-20 18:12 Thomas Hellstrom
2025-03-13 16:35 Rodrigo Vivi
2025-03-06 18:01 Rodrigo Vivi
2025-02-27 16:28 Rodrigo Vivi
2025-02-20 16:54 Rodrigo Vivi
2025-02-13 17:25 Rodrigo Vivi
2025-02-06 13:48 Rodrigo Vivi
2025-01-16 20:02 Thomas Hellstrom
2025-01-09 18:59 Thomas Hellstrom
2025-01-02 19:53 Thomas Hellstrom
2024-12-23 17:53 Thomas Hellstrom
2025-01-02 19:55 ` Thomas Hellström
2024-12-04 14:08 Thomas Hellstrom
2024-11-15  0:03 Lucas De Marchi
2024-11-08 15:28 Lucas De Marchi
2024-11-01 10:41 Lucas De Marchi
2024-10-24 23:15 Lucas De Marchi
2024-10-18  3:33 Lucas De Marchi
2024-10-11  3:12 Lucas De Marchi
2024-10-03 14:15 Lucas De Marchi
2024-09-12 14:46 Rodrigo Vivi
2024-09-05 13:28 Rodrigo Vivi
2024-08-29 13:59 Rodrigo Vivi
2024-08-22 15:12 Rodrigo Vivi
2024-08-15 14:02 Rodrigo Vivi
2024-08-08 17:55 Rodrigo Vivi
2024-07-11 22:16 Lucas De Marchi
2024-07-04 10:51 Thomas Hellstrom
2024-07-04 14:46 ` Daniel Vetter
2024-06-20  8:02 Thomas Hellstrom
2024-06-13 11:26 Thomas Hellstrom
2024-06-04 15:09 Thomas Hellstrom
2024-05-30 16:41 Thomas Hellstrom
2024-05-09 19:26 Lucas De Marchi
2024-05-02 16:37 Lucas De Marchi
2024-04-25 20:50 Lucas De Marchi
2024-04-18 15:47 Lucas De Marchi
2024-04-11 17:34 Lucas De Marchi
2024-04-04 14:49 Lucas De Marchi
2024-03-26 17:10 Lucas De Marchi
2024-03-07 10:48 Thomas Hellstrom
2024-02-29 13:07 Thomas Hellstrom
2024-02-22 11:12 Thomas Hellstrom
2024-02-15 12:43 Thomas Hellstrom
2024-02-08 11:08 Thomas Hellstrom
2024-02-01 11:37 Thomas Hellstrom
2024-02-01 11:37 ` Thomas Hellstrom
2024-02-01 11:42 ` Thomas Hellström
2024-02-01 11:42   ` Thomas Hellström
2024-01-25  8:29 Thomas Hellstrom
2024-01-25  8:29 ` Thomas Hellstrom

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=Z1s5elHXOyeIHnE0@fedora \
    --to=thomas.hellstrom@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=joonas.lahtinen@linux.intel.com \
    --cc=lucas.demarchi@intel.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=rodrigo.vivi@intel.com \
    --cc=simona.vetter@ffwll.ch \
    --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.