All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@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-xe-next-fixes
Date: Wed, 17 Jun 2026 12:17:45 -0700	[thread overview]
Message-ID: <ajLy2brwvOZEFNNN@gsse-cloud1.jf.intel.com> (raw)

Hi Dave, Sima,

Here are drm-xe-next-fixes for 7.2.

Matt

drm-xe-next-fixes-2026-06-17:
The following changes since commit 52d4ab1ca790a668cc8f2c27017138b1c467168c:

  Merge tag 'drm-misc-next-fixes-2026-06-11' of https://gitlab.freedesktop.org/drm/misc/kernel into drm-next (2026-06-13 08:10:38 +1000)

are available in the Git repository at:

  https://gitlab.freedesktop.org/drm/xe/kernel.git tags/drm-xe-next-fixes-2026-06-17

for you to fetch changes up to 0b5ed2756d45b04669502a1f13b1657ec7664571:

  drm/xe: Add compact-PT and addr mask handling for page reclaim (2026-06-16 10:18:52 -0700)

----------------------------------------------------------------

----------------------------------------------------------------
Brian Nguyen (1):
      drm/xe: Add compact-PT and addr mask handling for page reclaim

Daniele Ceraolo Spurio (1):
      Revert "drm/xe/nvls: Define GuC firmware for NVL-S"

Matthew Brost (1):
      drm/xe: Set TTM device beneficial_order to 9 (2M)

Niranjana Vishwanathapura (1):
      drm/xe/multi_queue: skip submit when primary queue is suspended

Raag Jadav (3):
      drm/xe/drm_ras: Make counter allocation drm managed
      drm/xe/drm_ras: Add per node cleanup action
      drm/xe/hw_error: Use HW_ERR prefix in log

Rodrigo Vivi (1):
      drm/xe: fix job timeout recovery for unstarted jobs and kernel queues

Tangudu Tilak Tirumalesh (3):
      Revert "drm/xe: Skip exec queue schedule toggle if queue is idle during suspend"
      drm/xe: Clear pending_disable before signaling suspend fence
      drm/xe: include all registered queues in TLB invalidation

Tejas Upadhyay (1):
      drm/xe/guc: Fix buffer overflow in steered register list allocation

Thomas Hellström (1):
      drm/xe: Fix wa_oob codegen recipe for external module builds

Wentao Liang (1):
      drm/xe: fix refcount leak in xe_range_fence_insert()

 drivers/gpu/drm/xe/Makefile             |   4 +-
 drivers/gpu/drm/xe/regs/xe_gtt_defs.h   |   6 +-
 drivers/gpu/drm/xe/xe_device.c          |   3 +-
 drivers/gpu/drm/xe/xe_drm_ras.c         |  61 ++++++---------
 drivers/gpu/drm/xe/xe_exec_queue.h      |  17 -----
 drivers/gpu/drm/xe/xe_guc_capture.c     |  10 ++-
 drivers/gpu/drm/xe/xe_guc_submit.c      | 111 +++++++++++----------------
 drivers/gpu/drm/xe/xe_guc_tlb_inval.c   |   7 +-
 drivers/gpu/drm/xe/xe_hw_engine_group.c |  10 +--
 drivers/gpu/drm/xe/xe_hw_error.c        |  12 +--
 drivers/gpu/drm/xe/xe_pt.c              | 131 +++++++++++++++++++-------------
 drivers/gpu/drm/xe/xe_range_fence.c     |   2 +
 drivers/gpu/drm/xe/xe_uc_fw.c           |   1 -
 13 files changed, 174 insertions(+), 201 deletions(-)

             reply	other threads:[~2026-06-17 19:17 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-17 19:17 Matthew Brost [this message]
2026-06-17 20:09 ` [PULL] drm-xe-next-fixes Matthew Brost
  -- strict thread matches above, loose matches on Subject: below --
2026-02-19 22:42 Rodrigo Vivi
2026-02-05 14:47 Rodrigo Vivi
2026-01-29 19:19 Rodrigo Vivi
2025-11-21  9:46 Thomas Hellstrom
2025-10-03 20:47 Lucas De Marchi
2025-08-06 13:24 Rodrigo Vivi
2025-07-31 19:46 Rodrigo Vivi
2025-06-05 19:07 Thomas Hellstrom
2025-05-28 16:21 Thomas Hellstrom
2025-05-23  8:25 Thomas Hellstrom
2025-03-27 15:14 Lucas De Marchi
2025-03-13  4:41 Lucas De Marchi
2024-11-28 15:39 Thomas Hellstrom
2024-11-21 19:39 Thomas Hellstrom
2024-11-15 11:10 Thomas Hellstrom
2024-09-20  2:56 Lucas De Marchi
2024-09-20  3:14 ` Lucas De Marchi
2024-09-12 23:23 Lucas De Marchi
2024-07-18 15:51 Rodrigo Vivi
2024-07-09 21:31 Rodrigo Vivi
2024-07-10 19:42 ` Lucas De Marchi
2024-07-10 20:45   ` Rodrigo Vivi
2024-05-09 16:35 Thomas Hellstrom
2024-05-02 14:26 Thomas Hellstrom
2024-03-15  4:14 Lucas De Marchi
2024-03-04 16:00 Lucas De Marchi
2024-01-16 10:22 Thomas Hellström
2024-01-16 10:22 ` Thomas Hellström
2023-12-26 18:27 Rodrigo Vivi

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=ajLy2brwvOZEFNNN@gsse-cloud1.jf.intel.com \
    --to=matthew.brost@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=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.