amdgpu_devi...ck_vram_lost(9)

📦 version 7.3.1, in nixpkgs unstable

✨ amdgpu_devi...ck_vram_lost(9) ✨

okay so bestie, welcome to the Kernel API Manual 💖 — yes that's the manual name, it's giving official-API-girlboss energy, and today we're doing amdgpu_device_check_vram_lost. it's a tiny little function but lowkey it's a whole vibe check for your GPU's memory. let's go 🫶

🌸 NAME 🌸

amdgpu_device_check_vram_lost — check if vram is valid 💅

🦋 SYNOPSIS 🦋

bool amdgpu_device_check_vram_lost (struct amdgpu_device *adev );

like, it takes one thing and returns a bool, that's the whole entire function, periodt ✨

🎀 ARGUMENTS 🎀

  • adev — amdgpu_device pointer 🌈 literally just your amdgpu device pointer, that's it, that's the argument

👑 DESCRIPTION 👑

so what does it do? ok so — it checks the reset magic value that got written to the gart pointer in VRAM 🔥

the driver calls this after a GPU reset to see whether the contents of VRAM is lost or now 💀 (yes the original says "or now", we're keeping it, it's iconic). it returns true if vram is lost, and false if not ⭐

tl;dr: magic value in VRAM → was it still there after the reset → you get your answer. it's giving "did my GPU just forget everything" energy and honestly? obsessed 🙈

💜 SEE ALSO 💜

Kernel file ./drivers/gpu/drm/amd/amdgpu/amdgpu_device.c

and now the friendship bracelet of cross-references, no cap, every single one, we do NOT skip the squad 🫶:

(ngl that list ate and left no crumbs 👑)

ok tiny note bestie: that stray "are … wait no" up there was me being a whole mess — the actual reference is amdgpu_device_is_peer_accessible(9), use that one 💖

🧚 sign-off 🧚

that's the page!! from ./drivers/gpu/drm/amd/amdgpu, dated October 2026, and the title on the tin is amdgpu_devi...ck_vram_lost(9) — ily, go check your VRAM, and slay 💅✨🍓

📦 where this page comes from