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>,
"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, 22 Jan 2026 13:52:25 +0100 [thread overview]
Message-ID: <aXIdiXaY-RxoaviV@fedora> (raw)
Hi Dave, Simona
The drm-xe-fixes for -rc7.
Some notable changes:
- There is an UAPI fix by Matt Auld that allows us to skip a hairy
fix in the driver that probably nobody would want to use anyway.
- Xe userptr was broken in 6.18 in the absence of CONFIG_DEVICE_PRIVATE.
that's a regression that causes problem for people. Fix included,
although some backporting had to be done so it conflicts a bit with
drm-next. Resolution in drm-rerere.
- There is a (perhaps somewhat late) to the SVM config logic. It's not
CC'd stable to avoid unlikely but possible side-effects from enabling
CONFIG_DEVICE_PRIVATE. The purpose is to make the XE SVM choice more
visible to increase the likelyhood of getting the code exercised and tested.
Thanks,
Thomas
drm-xe-fixes-2026-01-22:
UAPI Changes:
- Disallow bind-queue sharing across multiple VMs (Matt Auld)
Core Changes:
- Fix xe userptr in the absence of CONFIG_DEVICE_PRIVATE (Thomas)
Driver Changes:
- Fix a missed page count update (Matt Brost)
- Fix a confused argument to alloc_workqueue() (Marco Crivellari)
- Kernel-doc fixes (Jani)
- Disable a workaround on VFs (Matt Brost)
- Fix a job lock assert (Matt Auld)
- Update wedged.mode only after successful reset policy change (Lukasz)
- Select CONFIG_DEVICE_PRIVATE when DRM_XE_GPUSVM is selected (Thomas)
The following changes since commit 9dd1f5f3eb8cb175e2f7fd2a685bdb6b1bd2a726:
Merge tag 'drm-misc-fixes-2026-01-16' of https://gitlab.freedesktop.org/drm/misc/kernel into drm-fixes (2026-01-16 20:27:21 +0100)
are available in the Git repository at:
https://gitlab.freedesktop.org/drm/xe/kernel.git tags/drm-xe-fixes-2026-01-22
for you to fetch changes up to e27ada4f19e7ffda4c05ce8633daf6daed667eea:
drm/xe: Select CONFIG_DEVICE_PRIVATE when DRM_XE_GPUSVM is selected (2026-01-22 11:27:25 +0100)
----------------------------------------------------------------
UAPI Changes:
- Disallow bind-queue sharing across multiple VMs (Matt Auld)
Core Changes:
- Fix xe userptr in the absence of CONFIG_DEVICE_PRIVATE (Thomas)
Driver Changes:
- Fix a missed page count update (Matt Brost)
- Fix a confused argument to alloc_workqueue() (Marco Crivellari)
- Kernel-doc fixes (Jani)
- Disable a workaround on VFs (Matt Brost)
- Fix a job lock assert (Matt Auld)
- Update wedged.mode only after successful reset policy change (Lukasz)
- Select CONFIG_DEVICE_PRIVATE when DRM_XE_GPUSVM is selected (Thomas)
----------------------------------------------------------------
Jani Nikula (3):
drm/xe/vf: fix struct xe_gt_sriov_vf_migration kernel-doc
drm/xe/xe_late_bind_fw: fix enum xe_late_bind_fw_id kernel-doc
drm/xe/vm: fix xe_vm_validation_exec() kernel-doc
Lukasz Laguna (1):
drm/xe: Update wedged.mode only after successful reset policy change
Marco Crivellari (1):
drm/xe: fix WQ_MEM_RECLAIM passed as max_active to alloc_workqueue()
Matthew Auld (2):
drm/xe/uapi: disallow bind queue sharing
drm/xe/migrate: fix job lock assert
Matthew Brost (2):
drm/xe: Adjust page count tracepoints in shrinker
drm/xe: Disable timestamp WA on VFs
Thomas Hellström (2):
drm, drm/xe: Fix xe userptr in the absence of CONFIG_DEVICE_PRIVATE
drm/xe: Select CONFIG_DEVICE_PRIVATE when DRM_XE_GPUSVM is selected
drivers/gpu/drm/Kconfig | 2 +-
drivers/gpu/drm/Makefile | 4 +-
drivers/gpu/drm/xe/Kconfig | 5 ++-
drivers/gpu/drm/xe/xe_bo.c | 9 +++-
drivers/gpu/drm/xe/xe_debugfs.c | 72 +++++++++++++++++++++++-------
drivers/gpu/drm/xe/xe_device_types.h | 18 ++++++++
drivers/gpu/drm/xe/xe_exec_queue.c | 32 ++++++++++++-
drivers/gpu/drm/xe/xe_exec_queue.h | 1 +
drivers/gpu/drm/xe/xe_exec_queue_types.h | 6 +++
drivers/gpu/drm/xe/xe_ggtt.c | 2 +-
drivers/gpu/drm/xe/xe_gt_sriov_vf_types.h | 4 +-
drivers/gpu/drm/xe/xe_guc_ads.c | 14 +++---
drivers/gpu/drm/xe/xe_guc_ads.h | 5 ++-
drivers/gpu/drm/xe/xe_late_bind_fw_types.h | 4 +-
drivers/gpu/drm/xe/xe_lrc.c | 3 ++
drivers/gpu/drm/xe/xe_migrate.c | 4 +-
drivers/gpu/drm/xe/xe_sriov_vf_ccs.c | 2 +-
drivers/gpu/drm/xe/xe_vm.c | 7 ++-
drivers/gpu/drm/xe/xe_vm.h | 2 +-
include/drm/drm_pagemap.h | 19 +++++++-
20 files changed, 175 insertions(+), 40 deletions(-)
next reply other threads:[~2026-01-22 12:53 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 12:52 Thomas Hellstrom [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-26 12:03 [PULL] drm-xe-fixes 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
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:42 ` Thomas Hellström
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=aXIdiXaY-RxoaviV@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=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=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