From: Priya Hosur <Priya.Hosur@amd.com>
To: <amd-gfx@lists.freedesktop.org>, <Alexander.Deucher@amd.com>,
<Sunil.Khatri@amd.com>, <Felix.Kuehling@amd.com>,
<Shaoyun.Liu@amd.com>, <Lijo.Lazar@amd.com>,
<Mario.Limonciello@amd.com>, <Christian.Koenig@amd.com>
Cc: <Pratik.Vishwakarma@amd.com>,
<Veerabadhran.Gopalakrishnan@amd.com>, <Priya.Hosur@amd.com>
Subject: [PATCH v3 0/2] drm/amdkfd: Add TLB flush after MES queue eviction/suspension
Date: Fri, 14 Aug 2026 21:48:38 +0530 [thread overview]
Message-ID: <20260814161841.5906-1-Priya.Hosur@amd.com> (raw)
This patch series adds heavy-weight TLB flush after MES queue eviction/suspension
to fix SVM page migration hangs on gfx1151 with XNACK mode enabled.
v3:
- Split into 2 patches per Alex's review
- Added userq TLB flush in amdgpu_userq_unmap_helper() (amdgpu_userq.c)
v2:
- Removed "SDMA" from comment as this affects all in-flight memory
accesses, not just SDMA (Felix Kuehling)
- Added Reviewed-by tag
Priya Hosur (2):
drm/amdkfd: Add TLB flush after MES queue eviction/suspension
drm/amdgpu: Add TLB flush after MES user queue unmap
drivers/gpu/drm/amd/amdgpu/amdgpu_userq.c | 6 ++++++
.../gpu/drm/amd/amdkfd/kfd_device_queue_manager.c | 13 ++++++++++++-
2 files changed, 18 insertions(+), 1 deletion(-)
--
2.43.0
next reply other threads:[~2026-08-14 16:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 16:18 Priya Hosur [this message]
2026-08-14 16:18 ` [PATCH v3 1/2] drm/amdkfd: Add TLB flush after MES queue eviction/suspension Priya Hosur
2026-08-14 16:18 ` [PATCH v3 2/2] drm/amdgpu: Add TLB flush after MES user queue unmap Priya Hosur
2026-08-14 16:29 ` Lazar, Lijo
2026-08-14 16:47 ` Kuehling, Felix
2026-08-14 17:25 ` Lazar, Lijo
2026-08-16 17:07 ` Hosur, Priya
2026-08-17 14:19 ` Alex Deucher
2026-08-17 14:25 ` Khatri, Sunil
2026-08-24 7:39 ` Christian König
2026-08-25 6:47 ` Khatri, Sunil
2026-08-25 10:36 ` Hosur, Priya
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=20260814161841.5906-1-Priya.Hosur@amd.com \
--to=priya.hosur@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=Christian.Koenig@amd.com \
--cc=Felix.Kuehling@amd.com \
--cc=Lijo.Lazar@amd.com \
--cc=Mario.Limonciello@amd.com \
--cc=Pratik.Vishwakarma@amd.com \
--cc=Shaoyun.Liu@amd.com \
--cc=Sunil.Khatri@amd.com \
--cc=Veerabadhran.Gopalakrishnan@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
/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.