STRUCT MSM_GEM_VM_LOG_ENTRY(9)
πΈ struct msm_gem_vm_log_entry(9) πΈ
okay bestie, welcome to the Kernel API Manual π this one's a little struct page and it's honestly lowkey iconic, so let's get into it β¨
β¨ NAME β¨
struct msm_gem_vm_log_entry β literally just an entry in the VM log π that's the whole thing, that's the vibe π
π¦ SYNOPSIS π¦
struct msm_gem_vm_log_entry {
const char *op;
uint64_t iova;
uint64_t range;
int queue_id;
};
look at her π four fields, no cap, exactly as written β op, iova, range, queue_id, copy-pasted verbatim because we do not mess with the source fr fr π
π MEMBERS π
(ngl, this section is literally empty on the original page β the fields are all up there in the synopsis, so go peek at that πΈ)
π«Ά DESCRIPTION π«Ά
okay so here's the tea β for userspace managed VMs, there's a log tracking recent VM updates, and that log gets captured in GPU devcore dumps πΈ the whole point? to aid debugging issues caused by β and I quote the vibe β (for example) incorrectly synchronized VM updates π so basically when your VM updates aren't synced right, this log is the receipts bestie π§Ύβ¨
π SEE ALSO π
- Kernel file
./drivers/gpu/drm/msm/msm_gem.hπ struct msm_gem_vm(9)struct msm_gem_vma(9)msm_gem_lock_vm_and_obj(9)
go read those too, iykyk π
π reminder bestie: this is the Kernel API Manual page for struct msm_gem_vm_log_entry(9) β that's the manual name, that's the header, we stan a consistent title π
and that's a wrap! π¦ this page came from ./drivers/gpu/drm/msm, dated October 2026, and it's filed under struct msm_gem_vm_log_entry(9) β slay, ate, periodt π
β¨π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms