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>,
	"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-xe-next
Date: Thu, 8 May 2025 18:01:07 +0200	[thread overview]
Message-ID: <aBzUwbzCzz7Qo7fA@fedora> (raw)

Hi Dave, Simona

The probably last drm-xe-next PR towards 6.16.
Almost only fixes, except for the PCIe link downgrade attributes.

Thanks,
Thomas

drm-xe-next-2025-05-08:
UAPI Changes:
- Expose PCIe link downgrade attributes (Raag)

Cross-subsystem Changes:

Core Changes:
- gpusvm has_dma_mapping fix (Dafna)

Driver Changes:
- Forcewake hold fix (Tejas)
- Fix guc_info debugfs for VFs (Daniele)
- Fix devcoredump chunk alignment calculation (Arnd)
- Don't print timedout job message on killed exec queues (Matt Brost)
- Don't flush the GSC worker from the reset path (Daniele)
- Use copy_from_user() instead of __copy_from_user() (Harish)
- Only flush SVM garbage collector if CONFIG_DRM_XE_GPUSVM (Shuicheng)
- Fix forcewake vs runtime pm ref release ordering (Shuicheng)
- Move xe_device_sysfs_init() to xe_device_probe() (Raag)
- Append PCIe Gen5 limitations to xe_firmware document (Raag)
The following changes since commit 1bb53d05ba71b684f61bd11df8b99fe75ce52754:

  Merge drm/drm-next into drm-xe-next (2025-04-28 17:42:49 +0200)

are available in the Git repository at:

  https://gitlab.freedesktop.org/drm/xe/kernel.git tags/drm-xe-next-2025-05-08

for you to fetch changes up to 252c4711973de4e4f3ecddcc18912aecfd4e537c:

  drm/xe/doc: Wire up PCIe Gen5 limitations (2025-05-07 15:31:11 -0400)

----------------------------------------------------------------
UAPI Changes:
- Expose PCIe link downgrade attributes (Raag)

Cross-subsystem Changes:

Core Changes:
- gpusvm has_dma_mapping fix (Dafna)

Driver Changes:
- Forcewake hold fix (Tejas)
- Fix guc_info debugfs for VFs (Daniele)
- Fix devcoredump chunk alignment calculation (Arnd)
- Don't print timedout job message on killed exec queues (Matt Brost)
- Don't flush the GSC worker from the reset path (Daniele)
- Use copy_from_user() instead of __copy_from_user() (Harish)
- Only flush SVM garbage collector if CONFIG_DRM_XE_GPUSVM (Shuicheng)
- Fix forcewake vs runtime pm ref release ordering (Shuicheng)
- Move xe_device_sysfs_init() to xe_device_probe() (Raag)
- Append PCIe Gen5 limitations to xe_firmware document (Raag)

----------------------------------------------------------------
Arnd Bergmann (1):
      drm/xe: fix devcoredump chunk alignmnent calculation

Dafna Hirschfeld (1):
      drm/gpusvm: set has_dma_mapping inside mapping loop

Daniele Ceraolo Spurio (2):
      drm/xe/vf: Fix guc_info debugfs for VFs
      drm/xe/gsc: do not flush the GSC worker from the reset path

Harish Chegondi (1):
      drm/xe: Use copy_from_user() instead of __copy_from_user()

Matthew Brost (1):
      drm/xe: Do not print timedout job message on killed exec queues

Raag Jadav (3):
      drm/xe: Move xe_device_sysfs_init() to xe_device_probe()
      drm/xe: Expose PCIe link downgrade attributes
      drm/xe/doc: Wire up PCIe Gen5 limitations

Shuicheng Lin (2):
      drm/xe: Add config control for svm flush work
      drm/xe: Release force wake first then runtime power

Tejas Upadhyay (1):
      drm/xe/tests/mocs: Hold XE_FORCEWAKE_ALL for LNCF regs

 Documentation/gpu/xe/xe_firmware.rst |   6 ++
 drivers/gpu/drm/drm_gpusvm.c         |   2 +-
 drivers/gpu/drm/xe/tests/xe_mocs.c   |   7 ++-
 drivers/gpu/drm/xe/xe_bo.c           |   4 +-
 drivers/gpu/drm/xe/xe_devcoredump.c  |  13 +++--
 drivers/gpu/drm/xe/xe_device.c       |   5 ++
 drivers/gpu/drm/xe/xe_device_sysfs.c | 104 +++++++++++++++++++++++++++++++++--
 drivers/gpu/drm/xe/xe_eu_stall.c     |   4 +-
 drivers/gpu/drm/xe/xe_exec.c         |   4 +-
 drivers/gpu/drm/xe/xe_exec_queue.c   |   9 ++-
 drivers/gpu/drm/xe/xe_gsc.c          |  22 ++++++++
 drivers/gpu/drm/xe/xe_gsc.h          |   1 +
 drivers/gpu/drm/xe/xe_gsc_proxy.c    |  11 ++++
 drivers/gpu/drm/xe/xe_gsc_proxy.h    |   1 +
 drivers/gpu/drm/xe/xe_gt.c           |   2 +-
 drivers/gpu/drm/xe/xe_gt_debugfs.c   |   9 +--
 drivers/gpu/drm/xe/xe_guc.c          |  40 +++++++-------
 drivers/gpu/drm/xe/xe_guc_submit.c   |   9 ++-
 drivers/gpu/drm/xe/xe_oa.c           |   6 +-
 drivers/gpu/drm/xe/xe_pcode_api.h    |   5 ++
 drivers/gpu/drm/xe/xe_pm.c           |   8 +--
 drivers/gpu/drm/xe/xe_svm.c          |  13 ++++-
 drivers/gpu/drm/xe/xe_svm.h          |   6 ++
 drivers/gpu/drm/xe/xe_uc.c           |   8 ++-
 drivers/gpu/drm/xe/xe_uc.h           |   1 +
 drivers/gpu/drm/xe/xe_vm.c           |   9 ++-
 26 files changed, 241 insertions(+), 68 deletions(-)

             reply	other threads:[~2025-05-08 16:01 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-08 16:01 Thomas Hellstrom [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-05-14 13:20 [PULL] drm-xe-next Thomas Hellstrom
2026-04-30 13:00 Thomas Hellstrom
2026-03-27  3:24 Matthew Brost
2026-03-26  4:44 Matthew Brost
2026-03-12 14:57 Matthew Brost
2026-03-02 22:40 Matthew Brost
2026-01-15 16:16 Rodrigo Vivi
2025-12-30  9:58 Thomas Hellstrom
2025-12-19 22:41 Rodrigo Vivi
2025-11-14 10:49 Thomas Hellstrom
2025-11-17 20:56 ` Dave Airlie
2025-11-18  8:34   ` Thomas Hellström
2025-11-05 16:53 Thomas Hellstrom
2025-10-28 11:16 Thomas Hellstrom
2025-10-31 17:46 ` Simona Vetter
2025-10-20  8:31 Thomas Hellstrom
2025-10-24 11:26 ` Simona Vetter
2025-09-19 14:53 Lucas De Marchi
2025-08-29 22:00 Lucas De Marchi
2025-07-15 18:21 Rodrigo Vivi
2025-07-10 22:16 Rodrigo Vivi
2025-07-11  9:12 ` Simona Vetter
2025-07-11  9:25 ` Simona Vetter
2025-06-18 20:05 Rodrigo Vivi
2025-04-28 16:03 Thomas Hellstrom
2025-04-28 14:27 Thomas Hellstrom
2025-04-28 15:40 ` Thomas Hellström
2025-04-17 10:22 Thomas Hellstrom
2025-03-07  8:02 Lucas De Marchi
2025-03-07 14:51 ` Lucas De Marchi
2025-03-07 19:04   ` Lucas De Marchi
2025-02-24 18:50 Lucas De Marchi
2025-01-10 14:54 Rodrigo Vivi
2025-01-07 19:01 Rodrigo Vivi
2024-12-11 23:27 Rodrigo Vivi
2024-10-31 11:50 Thomas Hellstrom
2024-10-24 17:52 Thomas Hellstrom
2024-10-24 19:22 ` Matthew Brost
2024-10-25  7:30   ` Thomas Hellström
2024-10-25  9:34     ` Jani Nikula
2024-10-25 10:45       ` Thomas Hellström
2024-10-25 22:26         ` Matthew Brost
2024-10-17  9:32 Thomas Hellstrom
2024-10-10  9:56 Thomas Hellstrom
2024-09-06  2:29 Lucas De Marchi
2024-08-28 19:18 Lucas De Marchi
2024-08-22 20:55 Lucas De Marchi
2024-08-27 10:51 ` Daniel Vetter
2024-07-30 22:39 Lucas De Marchi
2024-07-02 19:02 Rodrigo Vivi
2024-07-05  8:18 ` Daniel Vetter
2024-06-26 22:32 Rodrigo Vivi
2024-06-06 21:43 Rodrigo Vivi
2024-04-23 12:54 Thomas Hellstrom
2024-02-26  3:21 Lucas De Marchi
2024-02-26  9:58 ` Daniel Vetter
2024-02-26 10:46 ` Daniel Stone
2024-02-26 14:16   ` Lucas De Marchi
2023-12-15 22:28 Rodrigo Vivi
2023-12-17 12:35 ` Oded Gabbay
2023-12-17 12:35   ` Oded Gabbay
2023-12-18 12:09 ` Oded Gabbay
2023-12-18 12:09   ` Oded Gabbay
2023-12-18 14:27 ` Oded Gabbay
2023-12-18 14:27   ` Oded Gabbay
2023-12-19  7:17   ` Ohad Sharabi
2023-12-19  9:15   ` Dani Liberman

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=aBzUwbzCzz7Qo7fA@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=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 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.