From: Donet Tom <donettom@linux.ibm.com>
To: amd-gfx@lists.freedesktop.org,
Felix Kuehling <Felix.Kuehling@amd.com>,
Alex Deucher <alexander.deucher@amd.com>,
Alex Deucher <alexdeucher@gmail.com>,
christian.koenig@amd.com, Philip Yang <yangp@amd.com>
Cc: David.YatSin@amd.com, Kent.Russell@amd.com,
Ritesh Harjani <ritesh.list@gmail.com>,
Vaidyanathan Srinivasan <svaidy@linux.ibm.com>,
Mukesh Kumar Chaurasiya <mkchauras@linux.ibm.com>,
donettom@linux.ibm.com
Subject: [PATCH v2 0/3] drm/amdkfd: Add support for non-4K page size systems - part1
Date: Mon, 12 Jan 2026 19:36:53 +0530 [thread overview]
Message-ID: <cover.1768223974.git.donettom@linux.ibm.com> (raw)
RFC -> v2
=========
In RFC patch v1 [1], there were 8 patches. From that series, patches 1–3 are
required to enable minimal support for 64K pages in AMDGPU. I have added those
3 pacthes in this series.
With these three patches applied, all RCCL tests and the rocr-debug-agent tests
pass on a ppc64le system with 64K page size on 2GPUs. However, on systems with
more than 2 GPUs and with XNACK enabled, we require additional Patches [4-8]
which were posted earlier as part of RFC [1] Since that require a bit of additional
work and discussion. We will post v2 of them later as Part-2.
1. Patch 1 was updated to only relax the EOP buffer size check, based on Philip Yang’s comment.
2. Philip’s review comments on Patch 2 were addressed, and Reviewed-by tags were added to
Patch 2 and Patch 3.
[1] https://lore.kernel.org/all/cover.1765519875.git.donettom@linux.ibm.com/
If this looks good, could we pull these changes into v6.20?
This patch series addresses few issues which we encountered while running rocr
debug agent and rccl unit tests with AMD GPU on Power10 (ppc64le), using 64k
system pagesize.
Note that we don't observe any of these issues while booting with 4k system
pagesize on Power. So with the 64K system pagesize what we observed so far is,
at few of the places, the conversion between gpu pfn to cpu pfn (or vice versa)
may not be done correctly (due to different page size of AMD GPU (4K)
v/s cpu pagesize (64K)) which causes issues like gpu page faults or gpu hang
while running these tests.
Changes so far in this series:
=============================
1. For now, during kfd queue creation, this patch lifts the restriction on EOP
buffer size to be same buffer object mapping size.
2. Fix SVM range map/unmap operations to convert CPU page numbers to GPU page
numbers before calling amdgpu_vm_update_range(), which expects 4K GPU pages.
Without this the rocr-debug-agent tests and rccl unit tests were failing.
3. Fix GART PTE allocation in migration code to account for multiple GPU pages
per CPU page. The current code only allocates PTEs based on number of CPU
pages, but GART may need one PTE per 4K GPU page.
Setup details:
============
System details: Power10 LPAR using 64K pagesize.
AMD GPU:
Name: gfx90a
Marketing Name: AMD Instinct MI210
Donet Tom (3):
drm/amdkfd: Relax size checking during queue buffer get
drm/amdkfd: Fix SVM map/unmap address conversion for non-4k page sizes
drm/amdkfd: Fix GART PTE for non-4K pagesize in svm_migrate_gart_map()
drivers/gpu/drm/amd/amdkfd/kfd_migrate.c | 2 +-
drivers/gpu/drm/amd/amdkfd/kfd_queue.c | 6 ++---
drivers/gpu/drm/amd/amdkfd/kfd_svm.c | 29 +++++++++++++++++-------
3 files changed, 25 insertions(+), 12 deletions(-)
--
2.52.0
next reply other threads:[~2026-01-12 14:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 14:06 Donet Tom [this message]
2026-01-12 14:06 ` [PATCH v2 1/3] drm/amdkfd: Relax size checking during queue buffer get Donet Tom
2026-01-12 14:06 ` [PATCH v2 2/3] drm/amdkfd: Fix SVM map/unmap address conversion for non-4k page sizes Donet Tom
2026-01-12 14:06 ` [PATCH v2 3/3] drm/amdkfd: Fix GART PTE for non-4K pagesize in svm_migrate_gart_map() Donet Tom
2026-01-12 20:28 ` [PATCH v2 0/3] drm/amdkfd: Add support for non-4K page size systems - part1 Felix Kuehling
2026-01-12 20:39 ` Alex Deucher
2026-01-13 8:10 ` Christian König
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=cover.1768223974.git.donettom@linux.ibm.com \
--to=donettom@linux.ibm.com \
--cc=David.YatSin@amd.com \
--cc=Felix.Kuehling@amd.com \
--cc=Kent.Russell@amd.com \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=mkchauras@linux.ibm.com \
--cc=ritesh.list@gmail.com \
--cc=svaidy@linux.ibm.com \
--cc=yangp@amd.com \
/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