All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@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-fixes
Date: Thu, 26 Feb 2026 08:09:51 -0500	[thread overview]
Message-ID: <aaBGHy_0RLGGIBP5@intel.com> (raw)

Hi Dave and Sima,

Here goes our first drm-xe-fixes PR for this 7.0 round.

Thanks,
Rodrigo.

drm-xe-fixes-2026-02-26:
- W/a fix for multi-cast registers (Roper)
- Fix xe_sync initialization issues (Shuicheng)
The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:

  Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)

are available in the Git repository at:

  https://gitlab.freedesktop.org/drm/xe/kernel.git tags/drm-xe-fixes-2026-02-26

for you to fetch changes up to 0879c3f04f67e2a1677c25dcc24669ce21eb6a6c:

  drm/xe/sync: Fix user fence leak on alloc failure (2026-02-23 16:48:43 -0500)

----------------------------------------------------------------
- W/a fix for multi-cast registers (Roper)
- Fix xe_sync initialization issues (Shuicheng)

----------------------------------------------------------------
Matt Roper (1):
      drm/xe/wa: Steer RMW of MCR registers while building default LRC

Shuicheng Lin (2):
      drm/xe/sync: Cleanup partially initialized sync on parse failure
      drm/xe/sync: Fix user fence leak on alloc failure

 drivers/gpu/drm/xe/regs/xe_engine_regs.h |  6 +++
 drivers/gpu/drm/xe/xe_gt.c               | 66 ++++++++++++++++++++++++++------
 drivers/gpu/drm/xe/xe_sync.c             | 30 ++++++++++-----
 3 files changed, 81 insertions(+), 21 deletions(-)

             reply	other threads:[~2026-02-26 13:10 UTC|newest]

Thread overview: 96+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-26 13:09 Rodrigo Vivi [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-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-12 19:28 Thomas Hellstrom
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=aaBGHy_0RLGGIBP5@intel.com \
    --to=rodrigo.vivi@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=matthew.brost@intel.com \
    --cc=mripard@kernel.org \
    --cc=ogabbay@kernel.org \
    --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.