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>,
donettom@linux.ibm.com
Subject: [PATCH v4 0/2] drm/amd: Add support for non-4K page size systems
Date: Thu, 26 Mar 2026 17:51:27 +0530 [thread overview]
Message-ID: <cover.1774521183.git.donettom@linux.ibm.com> (raw)
This is v4 of the patch series enabling 64 KB system page size
support.
v3 of this series [1] contained 6 patches, of which 4 have been
picked up and applied to drm-next. The initial minimal
infrastructure required for 64 KB page size support has already
been merged upstream [2].
This series includes the remaining fixes:
- Patch 1 fixes a kernel crash observed when running rocminfo
on systems with a 64 KB page size by updating the trap
reservation size.
- Patch 2 updates AMDGPU_GTT_MAX_TRANSFER_SIZE to always match
the PMD size across all page sizes.
Setup details:
==============
System details: Power10 LPAR using 64K pagesize.
AMD GPU:
Name: gfx90a
Marketing Name: AMD Instinct MI210
Changes since v3:
-----------------
- Based on feedback from Felix and Christian,
AMDGPU_VA_RESERVED_TRAP_SIZE has been updated. The virtual
address space now reserves 64 KB for the trap, while only
8 KB is allocated for both 4 KB and 64 KB page sizes. This
ensures that the allocation remains within the reserved
region.
Links:
------
[1] https://lore.kernel.org/all/cover.1774239489.git.donettom@linux.ibm.com/
[2] https://lore.kernel.org/all/cover.1765519875.git.donettom@linux.ibm.com/
Previous versions:
------------------
RFC v3 resend:
https://lore.kernel.org/all/cover.1774239489.git.donettom@linux.ibm.com/
RFC v3:
https://lore.kernel.org/all/cover.1771656655.git.donettom@linux.ibm.com/
RFC v2:
https://lore.kernel.org/all/cover.1769612973.git.donettom@linux.ibm.com/
RFC v1:
https://lore.kernel.org/all/cover.1765519875.git.donettom@linux.ibm.com/
Donet Tom (2):
drm/amdgpu: Change AMDGPU_VA_RESERVED_TRAP_SIZE to 64KB
drm/amdgpu: Fix AMDGPU_GTT_MAX_TRANSFER_SIZE for non-4K page size
drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 8 +++++---
drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.h | 2 +-
drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h | 2 +-
drivers/gpu/drm/amd/amdgpu/vce_v1_0.c | 3 ++-
drivers/gpu/drm/amd/amdkfd/kfd_priv.h | 4 ++--
5 files changed, 11 insertions(+), 8 deletions(-)
--
2.52.0
next reply other threads:[~2026-03-26 12:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 12:21 Donet Tom [this message]
2026-03-26 12:21 ` [PATCH v4 1/2] drm/amdgpu: Change AMDGPU_VA_RESERVED_TRAP_SIZE to 64KB Donet Tom
2026-03-26 12:36 ` Christian König
2026-03-26 13:47 ` Alex Deucher
2026-03-26 19:38 ` Kuehling, Felix
2026-03-26 12:21 ` [PATCH v4 2/2] drm/amdgpu: Fix AMDGPU_GTT_MAX_TRANSFER_SIZE for non-4K page size Donet Tom
2026-04-03 13:43 ` Donet Tom
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.1774521183.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=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