drm/amdgpu: add GART, GPUVM, and GTT to glossary
Subsystems (4)
Alex Deucher
maintainerPATCH 1/2 drm/amdgpu: add GART, GPUVM, and GTT to glossary
Add definitions to clarify GPU virtual memory.
v2: clarify the terms a bit more
Reviewed-by Luben Tuikov <[email protected]>
Suggested-by Peter Maucher <[email protected]>
Signed-off-by Alex Deucher <[email protected]>
--- Documentation/gpu/amdgpu/amdgpu-glossary.rst | 23 ++++++++++++++++++++ 1 file changed, 23 insertions(+)
Documentation/gpu/amdgpu/amdgpu-glossary.rst +23 -0
@@ -30,12 +30,35 @@ we have a dedicated glossary for Display Core at EOP End Of Pipe/Pipeline + GART + Graphics Address Remapping Table. This is the name we use for the GPUVM + page table used by the GPU kernel driver. It remaps system resources + (memory or MMIO space) into the GPU's address space so the GPU can access + them. The name GART harkens back to the days of AGP when the platform + provided an MMU that the GPU could use to get a contiguous view of + scattered pages for DMA. The MMU has since moved on to the GPU, but the + name stuck. + GC Graphics and Compute GMC Graphic Memory Controller + GPUVM + GPU Virtual Memory. This is the GPU's MMU. The GPU supports multiple + virtual address spaces that can be in flight at any given time. These + allow the GPU to remap VRAM and system resources into GPU virtual address + spaces for use by the GPU kernel driver and applications using the GPU. + These provide memory protection for different applications using the GPU. + + GTT + Graphics Translation Tables. This is a memory pool managed through TTM + which provides access to system resources (memory or MMIO space) for + use by the GPU. These addresses can be mapped into the "GART" GPUVM page + table for use by the kernel driver or into per process GPUVM page tables + for application usage. + IH Interrupt Handler
Signature · 1 line
2.38.1
Alex Deucher
maintainerPATCH 2/2 drm/amdgpu: expand on GPUVM documentation
Expand the GPUVM documentation to better describe the hardware functionality and use cases it serves.
Signed-off-by Alex Deucher <[email protected]>
--- drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 41 +++++++++++++++++++------- 1 file changed, 31 insertions(+), 10 deletions(-)
drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c +31 -10
@@ -45,22 +45,43 @@/** * DOC: GPUVM * -* GPUVM is similar to the legacy gart on older asics, however -* rather than there being a single global gart table -* for the entire GPU, there are multiple VM page tables active -* at any given time. The VM page tables can contain a mix -* vram pages and system memory pages and system memory pages +* GPUVM is the MMU functionality provided on the GPU. +* GPUVM is similar to the legacy GART on older asics, however +* rather than there being a single global GART table +* for the entire GPU, there can be multiple GPUVM page tables active +* at any given time. The GPUVM page tables can contain a mix +* VRAM pages and system pages (both memory and MMIO) and system pages * can be mapped as snooped (cached system pages) or unsnooped * (uncached system pages). -* Each VM has an ID associated with it and there is a page table -* associated with each VMID. When executing a command buffer, -* the kernel tells the ring what VMID to use for that command +* +* Each active GPUVM has an ID associated with it and there is a page table +* linked with each VMID. When executing a command buffer, +* the kernel tells the engine what VMID to use for that command * buffer. VMIDs are allocated dynamically as commands are submitted. * The userspace drivers maintain their own address space and the kernel * sets up their pages tables accordingly when they submit their * command buffers and a VMID is assigned. -* Cayman/Trinity support up to 8 active VMs at any given time; -* SI supports 16. +* The hardware supports up to 16 active GPUVMs at any given time. +* +* Each GPUVM is represented by a 1-2 or 1-5 level page table, depending +* on the ASIC family. GPUVM supports RWX attibutes on each page as well +* as other features such as encryption and caching attributes. +* +* VMID 0 is special. It is the GPUVM used for the kernel driver. In +* addition to an aperture managed by a page table, VMID 0 also has +* several other apertures. There is an aperture for direct access to VRAM +* and there is a legacy AGP aperture which just forwards accesses directly +* to the matching system physical addresses (or IOVAs when an IOMMU is +* present). These apertures provide direct access to these memories without +* incurring the overhead of a page table. VMID 0 is used by the kernel +* driver for tasks like memory management. +* +* GPU clients (i.e., engines on the GPU) use GPUVM VMIDs to access memory. +* For user applications, each application can have their own unqiue GPUVM +* address space. The application manages the address space and the kernel +* driver manages the GPUVM page tables for each process. If an GPU client +* accesses an invalid page, it will generate a GPU page fault, similar to +* accessing an invalid page on a CPU. */ #define START (node) ((node)->start)
Signature · 1 line
2.38.1
Re: [PATCH 2/2] drm/amdgpu: expand on GPUVM documentation
Reviewed-by Luben Tuikov <[email protected]>
Regards,
Luben
Quoted 66 lines · Alex Deucher
Expand the GPUVM documentation to better describe the hardware functionality and use cases it serves.
Signed-off-by Alex Deucher <[email protected]>--- drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 41 +++++++++++++++++++------- 1 file changed, 31 insertions(+), 10 deletions(-)drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c +31
-10@@ -45,22 +45,43 @@/** * DOC: GPUVM * -* GPUVM is similar to the legacy gart on older asics, however -* rather than there being a single global gart table -* for the entire GPU, there are multiple VM page tables active -* at any given time. The VM page tables can contain a mix -* vram pages and system memory pages and system memory pages +* GPUVM is the MMU functionality provided on the GPU. +* GPUVM is similar to the legacy GART on older asics, however +* rather than there being a single global GART table +* for the entire GPU, there can be multiple GPUVM page tables active +* at any given time. The GPUVM page tables can contain a mix +* VRAM pages and system pages (both memory and MMIO) and system pages * can be mapped as snooped (cached system pages) or unsnooped * (uncached system pages). -* Each VM has an ID associated with it and there is a page table -* associated with each VMID. When executing a command buffer, -* the kernel tells the ring what VMID to use for that command +* +* Each active GPUVM has an ID associated with it and there is a page table +* linked with each VMID. When executing a command buffer, +* the kernel tells the engine what VMID to use for that command * buffer. VMIDs are allocated dynamically as commands are submitted. * The userspace drivers maintain their own address space and the kernel * sets up their pages tables accordingly when they submit their * command buffers and a VMID is assigned. -* Cayman/Trinity support up to 8 active VMs at any given time; -* SI supports 16. +* The hardware supports up to 16 active GPUVMs at any given time. +* +* Each GPUVM is represented by a 1-2 or 1-5 level page table, depending +* on the ASIC family. GPUVM supports RWX attibutes on each page as well +* as other features such as encryption and caching attributes. +* +* VMID 0 is special. It is the GPUVM used for the kernel driver. In +* addition to an aperture managed by a page table, VMID 0 also has +* several other apertures. There is an aperture for direct access to VRAM +* and there is a legacy AGP aperture which just forwards accesses directly +* to the matching system physical addresses (or IOVAs when an IOMMU is +* present). These apertures provide direct access to these memories without +* incurring the overhead of a page table. VMID 0 is used by the kernel +* driver for tasks like memory management. +* +* GPU clients (i.e., engines on the GPU) use GPUVM VMIDs to access memory. +* For user applications, each application can have their own unqiue GPUVM +* address space. The application manages the address space and the kernel +* driver manages the GPUVM page tables for each process. If an GPU client +* accesses an invalid page, it will generate a GPU page fault, similar to +* accessing an invalid page on a CPU. */ #define START (node) ((node)->start)
Am 01.12.22 um 22:41 schrieb Alex Deucher:
Quoted 7 lines
Add definitions to clarify GPU virtual memory.
v2: clarify the terms a bit more
Reviewed-by Luben Tuikov <[email protected]>Suggested-by Peter Maucher <[email protected]>Signed-off-by Alex Deucher <[email protected]>
Quoted 44 lines
--- Documentation/gpu/amdgpu/amdgpu-glossary.rst | 23 ++++++++++++++++++++ 1 file changed, 23 insertions(+)Documentation/gpu/amdgpu/amdgpu-glossary.rst +23
-0@@ -30,12 +30,35 @@ we have a dedicated glossary for Display Core at EOP End Of Pipe/Pipeline + GART + Graphics Address Remapping Table. This is the name we use for the GPUVM + page table used by the GPU kernel driver. It remaps system resources + (memory or MMIO space) into the GPU's address space so the GPU can access + them. The name GART harkens back to the days of AGP when the platform + provided an MMU that the GPU could use to get a contiguous view of + scattered pages for DMA. The MMU has since moved on to the GPU, but the + name stuck. + GC Graphics and Compute GMC Graphic Memory Controller + GPUVM + GPU Virtual Memory. This is the GPU's MMU. The GPU supports multiple + virtual address spaces that can be in flight at any given time. These + allow the GPU to remap VRAM and system resources into GPU virtual address + spaces for use by the GPU kernel driver and applications using the GPU. + These provide memory protection for different applications using the GPU. + + GTT + Graphics Translation Tables. This is a memory pool managed through TTM + which provides access to system resources (memory or MMIO space) for + use by the GPU. These addresses can be mapped into the "GART" GPUVM page + table for use by the kernel driver or into per process GPUVM page tables + for application usage. + IH Interrupt Handler
Both patches are:
Reviewed-by Rajneesh Bhardwaj <[email protected]>
Quoted 51 lines · Alex Deucher
Add definitions to clarify GPU virtual memory.
v2: clarify the terms a bit more
Reviewed-by Luben Tuikov <[email protected]>Suggested-by Peter Maucher <[email protected]>Signed-off-by Alex Deucher <[email protected]>--- Documentation/gpu/amdgpu/amdgpu-glossary.rst | 23 ++++++++++++++++++++ 1 file changed, 23 insertions(+)Documentation/gpu/amdgpu/amdgpu-glossary.rst +23
-0@@ -30,12 +30,35 @@ we have a dedicated glossary for Display Core at EOP End Of Pipe/Pipeline + GART + Graphics Address Remapping Table. This is the name we use for the GPUVM + page table used by the GPU kernel driver. It remaps system resources + (memory or MMIO space) into the GPU's address space so the GPU can access + them. The name GART harkens back to the days of AGP when the platform + provided an MMU that the GPU could use to get a contiguous view of + scattered pages for DMA. The MMU has since moved on to the GPU, but the + name stuck. + GC Graphics and Compute GMC Graphic Memory Controller + GPUVM + GPU Virtual Memory. This is the GPU's MMU. The GPU supports multiple + virtual address spaces that can be in flight at any given time. These + allow the GPU to remap VRAM and system resources into GPU virtual address + spaces for use by the GPU kernel driver and applications using the GPU. + These provide memory protection for different applications using the GPU. + + GTT + Graphics Translation Tables. This is a memory pool managed through TTM + which provides access to system resources (memory or MMIO space) for + use by the GPU. These addresses can be mapped into the "GART" GPUVM page + table for use by the kernel driver or into per process GPUVM page tables + for application usage. + IH Interrupt Handler