Skip to content

next: show system memory use for integrated xe GPUs - #2210

Closed
anaveto wants to merge 1 commit into
flightlessmango:masterfrom
anaveto:fix/xe-integrated-memory
Closed

anaveto wants to merge 1 commit into
flightlessmango:masterfrom
anaveto:fix/xe-integrated-memory

Conversation

@anaveto

@anaveto anaveto commented Nov 14, 2026 •

Copy link
Copy Markdown
Contributor

On integrated Intel GPUs with the xe driver, VRAM always shows 0.0 GiB. An integrated GPU has no VRAM region. The GPU keeps its buffers in system memory. Example: an MSI Claw 8 EX (Panther Lake, kernel 7.3.3) in Enshrouded showed VRAM 0.0 GiB, while the game's fdinfo showed drm-resident-gtt: 6574360 KiB.

xe_drm_base::poll() already sends DRM_XE_DEVICE_QUERY_MEM_REGIONS. The reply also contains the system memory region. For that region, xe reports the usage of its TT manager: the system memory that the GPU uses (xe_query.c, query_mem_regions()). The change keeps that region. get_total_memory() and get_used_memory() return that region when the device has no VRAM region. GPUs with VRAM keep the same values.

The is_apu path (VRAM + GTT, as for AMD APUs) is not used here: for AMD, is_apu also selects the CPU power and the CPU temperature from the GPU metrics.

Testing:

🤖 model: claude-opus-5-5 | effort: xhigh

Integrated Intel GPUs on the xe driver, such as Lunar Lake and Panther
Lake, have no VRAM region, so VRAM always reads 0.0 GiB although a game
keeps several GiB of buffers in system memory.

The memory region query that is already polled also returns the system
memory region, whose used size is what the GPU has placed in system
memory (the TT manager's usage). Report that region when the device
has no VRAM region. GPUs with VRAM are unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@flightlessmango

Copy link
Copy Markdown
Owner

SYSMEM.used has different accounting semantics from our VRAM and GTT metrics. On this iGPU, Xe reports no dedicated VRAM region, so I’d leave the VRAM metric alone and skip this fallback.

@anaveto

anaveto commented Nov 15, 2026

Copy link
Copy Markdown
Contributor Author

Oh, that makes sense. Thank you, closing

@anaveto anaveto closed this Nov 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants