STRUCT MSM_GEM_VM_LOG_ENTRY(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 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 🌈

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