Searched refs:GPU (Results 1 – 25 of 149) sorted by relevance
123456
| /Linux-v6.6/Documentation/gpu/amdgpu/ |
| D | amdgpu-glossary.rst | 35 page table used by the GPU kernel driver. It remaps system resources
36 (memory or MMIO space) into the GPU's address space so the GPU can access
38 provided an MMU that the GPU could use to get a contiguous view of
39 scattered pages for DMA. The MMU has since moved on to the GPU, but the
49 GPU Virtual Memory. This is the GPU's MMU. The GPU supports multiple
51 allow the GPU to remap VRAM and system resources into GPU virtual address
52 spaces for use by the GPU kernel driver and applications using the GPU.
53 These provide memory protection for different applications using the GPU.
58 use by the GPU. These addresses can be mapped into the "GART" GPUVM page
|
| D | driver-misc.rst | 5 GPU Product Information
8 Information about the GPU can be obtained on certain cards
43 Discrete GPU Info
52 GPU Memory Usage Information
108 GPU SmartShift Information
111 GPU SmartShift information via sysfs
|
| D | thermal.rst | 2 GPU Power/Thermal Controls and Monitoring
11 GPU sysfs Power State Interfaces
14 GPU power controls are exposed via sysfs files.
89 If it's enabled, that means that the GPU is free to enter into GFXOFF mode as
95 Read it to check current GFXOFF's status of a GPU::
100 - 0: GPU is in GFXOFF state, the gfx engine is powered down.
122 interval the GPU was in GFXOFF mode. *Only supported in vangogh*
|
| D | driver-core.rst | 5 GPU Hardware Structure
17 the SoC itself rather than specific IPs. E.g., things like GPU resets
20 An APU contains more than just CPU and GPU, it also contains all of
22 components are shared between the CPU, platform, and the GPU (e.g.,
23 SMU, PSP, etc.). Specific components (CPU, GPU, etc.) usually have
29 With respect to the GPU, we have the following major IPs:
37 different IPs on the GPU get the memory (VRAM or system memory).
38 It also provides the support for per process GPU virtual address
42 This is the interrupt controller on the GPU. All of the IPs feed
62 various things including paging and GPU page table updates. It's also
[all …]
|
| /Linux-v6.6/Documentation/admin-guide/perf/ |
| D | nvidia-pmu.rst | 52 The NVLink-C2C0 PMU monitors incoming traffic from a GPU/CPU connected with
56 * NVIDIA Grace Hopper Superchip: Hopper GPU is connected with Grace SoC.
58 In this config, the PMU captures GPU ATS translated or EGM traffic from the GPU.
73 * Count event id 0x0 from the GPU/CPU connected with socket 0::
77 * Count event id 0x0 from the GPU/CPU connected with socket 1::
81 * Count event id 0x0 from the GPU/CPU connected with socket 2::
85 * Count event id 0x0 from the GPU/CPU connected with socket 3::
92 The NVLink-C2C1 PMU monitors incoming traffic from a GPU connected with
93 NVLink-C2C (Chip-2-Chip) interconnect. This PMU captures untranslated GPU
103 * Count event id 0x0 from the GPU connected with socket 0::
[all …]
|
| D | meson-ddr-pmu.rst | 28 + gpu - from 3D GPU
62 + Show individual DDR bandwidth from CPU and GPU respectively, as well as
|
| /Linux-v6.6/drivers/gpu/drm/virtio/ |
| D | Kconfig | 3 tristate "Virtio GPU driver"
10 This is the virtual GPU driver for virtio. It can be used with
16 bool "Virtio GPU driver modesetting support"
20 Enable modesetting support for virtio GPU driver. This can be
21 disabled in cases where only "headless" usage of the GPU is
|
| /Linux-v6.6/Documentation/driver-api/ |
| D | edac.rst | 116 Several stacks of HBM chips connect to the CPU or GPU through an ultra-fast
196 GPU nodes can be accessed the same way as the data fabric on CPU nodes.
199 and each GPU data fabric contains four Unified Memory Controllers (UMC).
207 Memory controllers on AMD GPU nodes can be represented in EDAC thusly:
209 GPU DF / GPU Node -> EDAC MC
210 GPU UMC -> EDAC CSROW
211 GPU UMC channel -> EDAC CHANNEL
218 - The CPU UMC (Unified Memory Controller) is mostly the same as the GPU UMC.
224 - GPU UMCs use 1 chip select, So UMC = EDAC CSROW.
225 - GPU UMCs use 8 channels, So UMC channel = EDAC channel.
[all …]
|
| /Linux-v6.6/Documentation/translations/zh_CN/mm/ |
| D | hmm.rst | 15 提供基础设施和帮助程序以将非常规内存（设备内存，如板上 GPU 内存）集成到常规内核路径中，其
20 必不可少，其中 GPU、DSP 或 FPGA 用于代表进程执行各种计算。
32 具有大量板载内存（几 GB）的设备（如 GPU）历来通过专用驱动程序特定 API 管理其内存。这会
40 具体来说，这意味着想要利用像 GPU 这样的设备的代码需要在通用分配的内存（malloc、mmap
56 序员干预的情况下利用 GPU 和其他设备。某些编译器识别的模式仅适用于共享地址空间。对所有
72 另一个严重的因素是带宽有限（约 32GBytes/s，PCIE 4.0 和 16 通道）。这比最快的 GPU
93 缓冲区池）并在其中写入 GPU 特定命令以执行更新（取消映射、缓存失效和刷新等）。这不能通
|
| /Linux-v6.6/Documentation/driver-api/thermal/ |
| D | nouveau_thermal.rst | 14 This driver allows to read the GPU core temperature, drive the GPU fan and
28 In order to protect the GPU from overheating, Nouveau supports 4 configurable
34 The GPU will be downclocked to reduce its power dissipation;
36 The GPU is put on hold to further lower power dissipation;
38 Shut the computer down to protect your GPU.
44 The default value for these thresholds comes from the GPU's vbios. These
|
| /Linux-v6.6/Documentation/gpu/ |
| D | msm-crash-dump.rst | 7 Following a GPU hang the MSM driver outputs debugging information via
35 ID of the GPU that generated the crash formatted as
39 The current value of RBBM_STATUS which shows what top level GPU
50 GPU address of the ringbuffer.
76 GPU address of the buffer object.
91 GPU memory region.
|
| D | v3d.rst | 8 GPU buffer object (BO) management
19 GPU Scheduling
|
| D | i915.rst | 267 Intel GPU Basics
270 An Intel GPU has multiple engines. There are several engine types.
284 The Intel GPU family is a family of integrated GPU's using Unified
285 Memory Access. For having the GPU "do work", user space will feed the
286 GPU batch buffers via one of the ioctls `DRM_IOCTL_I915_GEM_EXECBUFFER2`
288 instruct the GPU to perform work (for example rendering) and that work
291 `DRM_IOCTL_I915_GEM_CREATE`). An ioctl providing a batchbuffer for the GPU
306 Gen4, also have that a context carries with it a GPU HW context;
307 the HW context is essentially (most of at least) the state of a GPU.
308 In addition to the ordering guarantees, the kernel will restore GPU
[all …]
|
| /Linux-v6.6/drivers/gpu/drm/amd/amdkfd/ |
| D | Kconfig | 7 bool "HSA kernel driver for AMD GPU devices"
13 Enable this if you want to use HSA features on AMD GPU devices.
29 bool "HSA kernel driver support for peer-to-peer for AMD GPU devices"
33 the PCIe bus. This can improve performance of multi-GPU compute
|
| /Linux-v6.6/arch/arm64/boot/dts/qcom/ |
| D | msm8996-v3.0.dtsi | 13 * This revision seems to have differ GPU CPR
14 * parameters, GPU frequencies and some differences
16 * the GPU. Funnily enough, it's simpler to make it an
|
| /Linux-v6.6/arch/arm/boot/dts/rockchip/ |
| D | rk3288-veyron-mickey.dts | 86 * and don't let the GPU go faster than 400 MHz.
103 * the CPU and the GPU.
139 /* At very hot, don't let GPU go over 300 MHz */
180 /* After 1st level throttle the GPU down to as low as 400 MHz */
187 * Slightly after we throttle the GPU, we'll also make sure that
189 * throttle the CPU lower than 1.4 GHz due to GPU heat--we'll
200 /* When hot, GPU goes down to 300 MHz */
206 /* When really hot, don't let GPU go _above_ 300 MHz */
|
| /Linux-v6.6/Documentation/gpu/rfc/ |
| D | i915_vm_bind.rst | 8 objects (BOs) or sections of a BOs at specified GPU virtual addresses on a
10 mappings) will be persistent across multiple GPU submissions (execbuf calls)
30 * Support capture of persistent mappings in the dump upon GPU error.
96 newer VM_BIND mode, the VM_BIND mode with GPU page faults and possible future
108 In future, when GPU page faults are supported, we can potentially use a
124 When GPU page faults are supported, the execbuf path do not take any of these
166 implement Vulkan's Sparse Resources. With increasing GPU hardware performance,
180 Where GPU page faults are not available, kernel driver upon buffer invalidation
190 waiting process. User fence can be signaled either by the GPU or kernel async
199 Allows compute UMD to directly submit GPU jobs instead of through execbuf
[all …]
|
| /Linux-v6.6/drivers/gpu/drm/qxl/ |
| D | Kconfig | 3 tristate "QXL virtual GPU"
10 QXL virtual GPU for Spice virtualization desktop integration.
|
| /Linux-v6.6/drivers/gpu/drm/sti/ |
| D | NOTES | 23 GPU >-------------+GDP Main | | +---+ HDMI +--> HDMI
24 GPU >-------------+GDP mixer+---+ | :===========:
25 GPU >-------------+Cursor | | +---+ DVO +--> 24b//
|
| /Linux-v6.6/Documentation/ABI/testing/ |
| D | sysfs-platform-asus-wmi | 66 Switch the GPU hardware MUX mode. Laptops with this feature can
70 * 0 - Discrete GPU,
78 Disable discrete GPU:
87 Enable the external GPU paired with ROG X-Flow laptops.
|
| /Linux-v6.6/Documentation/gpu/amdgpu/display/ |
| D | dc-glossary.rst | 36 * SOCCLK: GPU Engine Clock
99 discrete GPU
144 integrated GPU
|
| /Linux-v6.6/drivers/gpu/drm/vc4/ |
| D | Kconfig | 24 VC4 GPU, such as the Raspberry Pi or other BCM2708/BCM2835.
35 Choose this option if you have a Broadcom VC4 GPU
|
| /Linux-v6.6/Documentation/accel/ |
| D | introduction.rst | 11 These devices can be either stand-alone ASICs or IP blocks inside an SoC/GPU.
24 type of device can be stand-alone or an IP inside a SoC or a GPU. It will
55 drivers can be of use to GPU drivers as well.
61 from trying to use an accelerator as a GPU, the compute accelerators will be
|
| /Linux-v6.6/drivers/gpu/drm/i915/ |
| D | Kconfig | 90 bool "Enable capturing GPU state following a hang"
94 This option enables capturing the GPU state when a hang is detected.
102 bool "Compress GPU error state"
108 selected and causes any error state captured upon a GPU hang
|
| D | Kconfig.profile | 46 check the health of the GPU and undertake regular house-keeping of
52 May be 0 to disable heartbeats and therefore disable automatic GPU
96 Before sleeping waiting for a request (GPU operation) to complete,
114 the GPU, we allow the innocent contexts also on the system to quiesce.
|
123456
