From: Alex Deucher <alexander.deucher@amd.com>
To: <amd-gfx@lists.freedesktop.org>,
<dri-devel@lists.freedesktop.org>, <airlied@gmail.com>,
<simona.vetter@ffwll.ch>
Cc: Alex Deucher <alexander.deucher@amd.com>
Subject: [pull] amdgpu, amdkfd drm-fixes-6.18
Date: Wed, 12 Nov 2025 15:09:30 -0500 [thread overview]
Message-ID: <20251112200930.8788-1-alexander.deucher@amd.com> (raw)
Hi Dave, Simona,
Fixes for 6.18.
The following changes since commit e9a6fb0bcdd7609be6969112f3fbfcce3b1d4a7c:
Linux 6.18-rc5 (2025-11-09 15:10:19 -0800)
are available in the Git repository at:
https://gitlab.freedesktop.org/agd5f/linux.git tags/amd-drm-fixes-6.18-2025-11-12
for you to fetch changes up to eac32ff42393efa6657efc821231b8d802c1d485:
drm/amdkfd: Fix GPU mappings for APU after prefetch (2025-11-11 22:52:51 -0500)
----------------------------------------------------------------
amd-drm-fixes-6.18-2025-11-12:
amdgpu:
- Disallow P2P DMA for GC 12 DCC surfaces
- ctx error handling fix
- UserQ fixes
- VRR fix
- ISP fix
- JPEG 5.0.1 fix
amdkfd:
- Save area check fix
- Fix GPU mappings for APU after prefetch
----------------------------------------------------------------
Harish Kasiviswanathan (1):
drm/amdkfd: Fix GPU mappings for APU after prefetch
Ivan Lipski (1):
drm/amd/display: Allow VRR params change if unsynced with the stream
Jesse.Zhang (1):
drm/amdgpu: fix lock warning in amdgpu_userq_fence_driver_process
Jonathan Kim (1):
drm/amdkfd: relax checks for over allocation of save area
Pierre-Eric Pelloux-Prayer (1):
drm/amdgpu: jump to the correct label on failure
Sathishkumar S (1):
drm/amdgpu/jpeg: Add parse_cs for JPEG5_0_1
Sultan Alsawaf (1):
drm/amd/amdgpu: Ensure isp_kernel_buffer_alloc() creates a new BO
Vitaly Prosyak (1):
drm/amdgpu: disable peer-to-peer access for DCC-enabled GC12 VRAM surfaces
drivers/gpu/drm/amd/amdgpu/amdgpu_ctx.c | 2 +-
drivers/gpu/drm/amd/amdgpu/amdgpu_dma_buf.c | 12 ++++++++++++
drivers/gpu/drm/amd/amdgpu/amdgpu_isp.c | 2 ++
drivers/gpu/drm/amd/amdgpu/amdgpu_userq_fence.c | 5 +++--
drivers/gpu/drm/amd/amdgpu/jpeg_v5_0_1.c | 1 +
drivers/gpu/drm/amd/amdkfd/kfd_queue.c | 12 ++++++------
drivers/gpu/drm/amd/amdkfd/kfd_svm.c | 2 ++
drivers/gpu/drm/amd/display/modules/freesync/freesync.c | 11 +++++++++++
8 files changed, 38 insertions(+), 9 deletions(-)
next reply other threads:[~2025-11-12 20:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 20:09 Alex Deucher [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-06 20:13 [pull] amdgpu, amdkfd drm-fixes-6.18 Alex Deucher
2025-10-16 13:22 Alex Deucher
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=20251112200930.8788-1-alexander.deucher@amd.com \
--to=alexander.deucher@amd.com \
--cc=airlied@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=simona.vetter@ffwll.ch \
/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