From: "Thomas Hellström" <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>,
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: Re: [PULL] drm-xe-next
Date: Mon, 28 Apr 2025 17:40:07 +0200 [thread overview]
Message-ID: <ee418b94f1952f12eccc340edab8405e76426565.camel@linux.intel.com> (raw)
In-Reply-To: <aA-QSfTtn0otDRM1@fedora>
On Mon, 2025-04-28 at 16:27 +0200, Thomas Hellstrom wrote:
> Hi Dave, Simona
>
> An additional drm-xe-next PR as requested on IRC.
> A lot of fixes but some new stuff as detailed below.
>
> Please note that the top commit,
>
> "Drop force_alloc from xe_bo_evict in selftests"
>
> carries a Fixes tag that is not an ancestor, but that
> commit is in drm-next so should not be a problem once
> merged, I hope.
>
> Thanks,
> Thomas
>
> drm-xe-next-2025-04-28:
> Core Changes:
> - Add drm_coredump_printer_is_full() (Matt Brost)
>
> Driver Changes:
> - Do not queue unneeded terminations from debugfs (Daniele)
> - Fix out-of-bound while enabling engine activity stats (Michal)
> - Use GT oriented message to report engine activity error (Michal)
> - Some fault-injection additions (Satyanarayana)
> - Fix an error pointer dereference (Harshit)
> - Fix capture of steering registers (John)
> - Use the steering flag when printing registers (John)
> - Cache DSS info when creating capture register list (John)
> - Backup VRAM in PM notifier instead of in the suspend / freeze
> callbacks (Matt Auld)
> - Fix CFI violation when accessing sysfs files (Jeevaka)
> - Fix kernel version docs for temperature and fan speed (Lucas)
> - Add devcoredump chunking (Matt Brost)
> - Update xe_ttm_access_memory to use GPU for non-visible access
> (Matt Brost)
> - Abort printing coredump in VM printer output if full (Matt Brost)
> - Resolve a possible circular locking dependency (Harish)
> - Don't support EU stall on SRIOV VF (Harish)
> - Drop force_alloc from xe_bo_evict in selftests (Matt Brost)
> The following changes since commit
> d755887f8e5a2a18e15e6632a5193e5feea18499:
>
> drm/xe/dma_buf: stop relying on placement in unmap (2025-04-16
> 09:59:24 +0100)
>
> are available in the Git repository at:
>
> https://gitlab.freedesktop.org/drm/xe/kernel.git tags/drm-xe-next-
> 2025-04-28
>
> for you to fetch changes up to
> 84a11c519234bfa3f6971f30d1a7c84077a4d681:
>
> drm/xe: Drop force_alloc from xe_bo_evict in selftests (2025-04-27
> 19:39:06 -0700)
>
> ----------------------------------------------------------------
> Core Changes:
> - Add drm_coredump_printer_is_full() (Matt Brost)
>
> Driver Changes:
> - Do not queue unneeded terminations from debugfs (Daniele)
> - Fix out-of-bound while enabling engine activity stats (Michal)
> - Use GT oriented message to report engine activity error (Michal)
> - Some fault-injection additions (Satyanarayana)
> - Fix an error pointer dereference (Harshit)
> - Fix capture of steering registers (John)
> - Use the steering flag when printing registers (John)
> - Cache DSS info when creating capture register list (John)
> - Backup VRAM in PM notifier instead of in the suspend / freeze
> callbacks (Matt Auld)
> - Fix CFI violation when accessing sysfs files (Jeevaka)
> - Fix kernel version docs for temperature and fan speed (Lucas)
> - Add devcoredump chunking (Matt Brost)
> - Update xe_ttm_access_memory to use GPU for non-visible access
> (Matt Brost)
> - Abort printing coredump in VM printer output if full (Matt Brost)
> - Resolve a possible circular locking dependency (Harish)
> - Don't support EU stall on SRIOV VF (Harish)
> - Drop force_alloc from xe_bo_evict in selftests (Matt Brost)
>
> ----------------------------------------------------------------
> Daniele Ceraolo Spurio (1):
> drm/xe/pxp: do not queue unneeded terminations from debugfs
>
> Harish Chegondi (2):
> drm/xe/eustall: Resolve a possible circular locking dependency
> drm/xe/eustall: Do not support EU stall on SRIOV VF
>
> Harshit Mogalapalli (1):
> drm/xe/svm: fix dereferencing error pointer in
> drm_gpusvm_range_alloc()
>
> Jeevaka Prabu Badrappan (1):
> drm/xe: Fix CFI violation when accessing sysfs files
>
> John Harrison (3):
> drm/xe/guc: Fix capture of steering registers
> drm/xe/guc: Use the steering flag when printing registers
> drm/xe/guc: Cache DSS info when creating capture register list
>
> Lucas De Marchi (2):
> drm/xe/hwmon: Fix kernel version documentation for temperature
> drm/xe/hwmon: Fix kernel version documentation for fan speed
>
> Matthew Auld (3):
> drm/xe: evict user memory in PM notifier
> drm/xe: share bo dma-resv with backup object
> drm/xe: handle pinned memory in PM notifier
>
> Matthew Brost (5):
> drm/xe: Add devcoredump chunking
> drm/xe: Update xe_ttm_access_memory to use GPU for non-visible
> access
> drm/print: Add drm_coredump_printer_is_full
> drm/xe: Abort printing coredump in VM printer output if full
> drm/xe: Drop force_alloc from xe_bo_evict in selftests
>
> Michal Wajdeczko (2):
> drm/xe/guc: Fix out-of-bound while enabling engine activity
> stats
> drm/xe: Use GT oriented message to report engine activity error
>
> Satyanarayana K V P (2):
> drm/xe: Introduce fault injection for guc mmio send/recv.
> drm/xe: Introduce fault injection for guc CTB send/recv
>
> Thomas Hellström (1):
> Merge drm/drm-next into drm-xe-next
>
> .clang-format | 7 +
> .gitignore
Please ignore this PR since the diffstat got excessively long. Probably
because that back-merge above was done before the previous PR was in.
I'll generate a new one.
/Thomas
next prev parent reply other threads:[~2025-04-28 15:40 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 14:27 [PULL] drm-xe-next Thomas Hellstrom
2025-04-28 15:40 ` Thomas Hellström [this message]
-- strict thread matches above, loose matches on Subject: below --
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-05-08 16:01 Thomas Hellstrom
2025-04-28 16:03 Thomas Hellstrom
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
2023-12-15 22:28 Rodrigo Vivi
2023-12-17 12:35 ` Oded Gabbay
2023-12-18 12:09 ` 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=ee418b94f1952f12eccc340edab8405e76426565.camel@linux.intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).