From: SRINIVASAN SHANMUGAM <srinivasan.shanmugam@amd.com>
To: "Lazar, Lijo" <lijo.lazar@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"Alex Deucher" <alexander.deucher@amd.com>
Cc: amd-gfx@lists.freedesktop.org,
"Timur Kristóf" <timur.kristof@gmail.com>,
"Samuel Pitoiset" <hakzsam@gmail.com>,
"Natalie Vock" <natalie.vock@gmx.de>
Subject: Re: [PATCH 1/3] drm/amdgpu: Add per-VM kernel queue first-level trap handler infrastructure
Date: Wed, 9 Sep 2026 18:32:03 +0530 [thread overview]
Message-ID: <b652b617-de17-4e11-9492-ffb003a9e51e@amd.com> (raw)
In-Reply-To: <4f97a5e8-8bef-4353-9998-9e6daee499d2@amd.com>
[-- Attachment #1: Type: text/plain, Size: 5820 bytes --]
On 9/9/2026 1:15 PM, Lazar, Lijo wrote:
>
>
> On 05-Sep-26 1:49 PM, Srinivasan Shanmugam wrote:
>> MES owns kernel queue VMIDs (1..first_kfd_vmid-1) but does not program
>> SQ_SHADER_TBA/TMA for them. On GFX11+ hardware MES maps kernel queues
>> via ADD_QUEUE with map_legacy_kq=1 but does not set trap handler state.
>> On GFX10 and earlier HWS-based hardware, the driver programs trap
>> registers via SRBM select for KFD queues but no equivalent exists for
>> driver-managed kernel queue VMIDs.
>>
>> Add a vmhub callback program_kernel_trap_vmids() so each gfxhub version
>> can write SQ_SHADER_TBA/TMA for kernel VMIDs. The TBA points to the
>> device-level CWSR ISA BO. The TMA is set to the fixed per-VM virtual
>> address AMDGPU_VA_RESERVED_TRAP_START — each VM maps its own kq_tma_bo
>> there, so per-VM isolation is handled entirely by page tables without
>> needing to reprogram the register per job or per submission.
>>
>> The per-VM kq_tma_bo is a small GTT BO allocated at VM creation time
>> (parallel to page table allocation) and mapped read-only into the GPU VM
>> at AMDGPU_VA_RESERVED_TRAP_START. The kernel CPU writes the second-level
>> handler address into it via kq_tma_map when userspace calls SET_L2_TRAP.
>> The first-level CWSR handler reads this address to chain to the
>> second-level handler when a shader exception fires.
>>
>> This design is:
>> - Per-VM BO (not device-level) — same model as page tables
>> - Fixed VA in each VM's address space — same VA, different
>> physical BO
>> - Read-only from GPU — kernel CPU updates it via CPU mapping
>> - Treat allocation/free lifecycle identical to page tables
>>
>> Suggested-by: Christian König <christian.koenig@amd.com>
>> Suggested-by: Alexander Deucher <alexander.deucher@amd.com>
>> Cc: Lijo Lazar <lijo.lazar@amd.com>
>> Cc: Timur Kristóf <timur.kristof@gmail.com>
>> Cc: Samuel Pitoiset <hakzsam@gmail.com>
>> Cc: Natalie Vock <natalie.vock@gmx.de>
>> Signed-off-by: Srinivasan Shanmugam <srinivasan.shanmugam@amd.com>
>> Change-Id: I9ce352157c4aa84099cef926cba61264781e8ad9
>> ---
>> drivers/gpu/drm/amd/amdgpu/amdgpu_gmc.h | 1 +
>> drivers/gpu/drm/amd/amdgpu/amdgpu_trap.c | 80 ++++++++++++++++++++++++
>> drivers/gpu/drm/amd/amdgpu/amdgpu_trap.h | 7 +++
>> drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 9 +++
>> drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h | 13 ++++
>> 5 files changed, 110 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_gmc.h
>> b/drivers/gpu/drm/amd/amdgpu/amdgpu_gmc.h
>> index 3ca187f5ade8..5624a5ab5c62 100644
>> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_gmc.h
>> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_gmc.h
>> @@ -115,6 +115,7 @@ struct amdgpu_vmhub_funcs {
>> void (*print_l2_protection_fault_status)(struct amdgpu_device
>> *adev,
>> uint32_t status);
>> uint32_t (*get_invalidate_req)(unsigned int vmid, uint32_t
>> flush_type);
>> + void (*program_kernel_trap_vmids)(struct amdgpu_device *adev);
>> };
>> struct amdgpu_vmhub {
>> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_trap.c
>> b/drivers/gpu/drm/amd/amdgpu/amdgpu_trap.c
>> index 623cac6781be..e913488ca3fa 100644
>> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_trap.c
>> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_trap.c
>> @@ -263,6 +263,7 @@ int amdgpu_trap_init(struct amdgpu_device *adev)
>> amdgpu_trap_cwsr_init_save_area_info(adev, trap_info);
>> adev->trap_info = no_free_ptr(trap_info);
>> + amdgpu_trap_program_kernel_vmids(adev);
>> return 0;
>> }
>> @@ -277,6 +278,85 @@ void amdgpu_trap_fini(struct amdgpu_device *adev)
>> adev->trap_info = NULL;
>> }
>> +void amdgpu_trap_program_kernel_vmids(struct amdgpu_device *adev)
>> +{
>> + struct amdgpu_vmhub *hub = &adev->vmhub[AMDGPU_GFXHUB(0)];
>> +
>> + if (!amdgpu_trap_is_enabled(adev))
>> + return;
>> + if (!hub->vmhub_funcs ||
>> !hub->vmhub_funcs->program_kernel_trap_vmids)
>> + return;
>> +
>> + hub->vmhub_funcs->program_kernel_trap_vmids(adev);
>> +}
>> +
>> +int amdgpu_trap_vm_kq_tma_alloc(struct amdgpu_device *adev,
>> + struct amdgpu_vm *vm)
>> +{
>> + void *cpu_addr;
>> + uint64_t va;
>> + int r;
>> +
>> + dma_resv_assert_held(vm->root.bo->tbo.base.resv);
>> +
>> + r = amdgpu_bo_create_kernel(adev, AMDGPU_GPU_PAGE_SIZE, PAGE_SIZE,
>> + AMDGPU_GEM_DOMAIN_GTT, &vm->kq_tma_bo,
>> + NULL, &cpu_addr);
>> + if (r)
>> + return r;
>> +
>> + if (vm->kq_tma_bo->kmap.bo_kmap_type & TTM_BO_MAP_IOMEM_MASK)
>> + iosys_map_set_vaddr_iomem(&vm->kq_tma_map,
>> + (void __iomem *)cpu_addr);
>> + else
>> + iosys_map_set_vaddr(&vm->kq_tma_map, cpu_addr);
>> +
>> + vm->kq_tma_va = amdgpu_vm_bo_add(adev, vm, vm->kq_tma_bo);
>> + if (!vm->kq_tma_va) {
>> + r = -ENOMEM;
>> + goto err_free_bo;
>> + }
>> +
>> + va = AMDGPU_VA_RESERVED_TRAP_START(adev) & AMDGPU_GMC_HOLE_MASK;
>
> Is this the same address used for mapping of TMA for user queues?
No — these are *different, non-overlapping addresses* in the reserved VA
region:
* |AMDGPU_VA_RESERVED_TRAP_UQ_START| = TRAP_START − 12 KiB
→ used for UQ first-level TBA (8 KiB) + TMA (4 KiB)
* |AMDGPU_VA_RESERVED_TRAP_START| = SEQ64_START − 64 KiB
→ used for KQ per-VM TMA (this patch)
The UQ region sits immediately below the KQ region in the reserved VA
space. No collision between the two mappings in the same VM.
Regards, Srini
[-- Attachment #2: Type: text/html, Size: 10239 bytes --]
next prev parent reply other threads:[~2026-09-09 13:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 8:19 [PATCH 0/3] drm/amdgpu: Second-level trap handler for kernel queues Srinivasan Shanmugam
2026-09-05 8:19 ` [PATCH 1/3] drm/amdgpu: Add per-VM kernel queue first-level trap handler infrastructure Srinivasan Shanmugam
2026-09-09 7:45 ` Lazar, Lijo
2026-09-09 13:02 ` SRINIVASAN SHANMUGAM [this message]
2026-09-09 17:58 ` Lazar, Lijo
2026-09-09 18:54 ` Alex Deucher
2026-09-10 2:06 ` Lazar, Lijo
2026-09-10 5:23 ` Lazar, Lijo
2026-09-11 14:07 ` Alex Deucher
2026-09-11 14:09 ` Alex Deucher
2026-09-11 15:17 ` Lazar, Lijo
2026-09-09 19:23 ` Alex Deucher
2026-09-09 20:39 ` Alex Deucher
2026-09-09 20:42 ` Alex Deucher
2026-09-09 20:50 ` Alex Deucher
2026-09-10 6:13 ` SRINIVASAN SHANMUGAM
2026-09-10 6:57 ` Lazar, Lijo
2026-09-10 8:25 ` SRINIVASAN SHANMUGAM
2026-09-10 9:43 ` Lazar, Lijo
2026-09-10 9:43 ` Lazar, Lijo
2026-09-11 14:41 ` Alex Deucher
2026-09-05 8:19 ` [PATCH 2/3] drm/amdgpu: Implement kernel VMID SQ_SHADER_TBA/TMA programming for GFX10/11/12 Srinivasan Shanmugam
2026-09-09 20:38 ` Alex Deucher
2026-09-05 8:19 ` [PATCH 3/3] drm/amdgpu: Extend second-level trap handler to kernel queues Srinivasan Shanmugam
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=b652b617-de17-4e11-9492-ffb003a9e51e@amd.com \
--to=srinivasan.shanmugam@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=hakzsam@gmail.com \
--cc=lijo.lazar@amd.com \
--cc=natalie.vock@gmx.de \
--cc=timur.kristof@gmail.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