TAPSET::MEMORY(3stap)

💖 NAME 💖

okay bestie, welcome to tapset::memory — it's the systemtap memory tapset, and it's literally the whole vibe of peeking at everything your kernel does with memory. this is from the 3stap manual, section 3, tapset girlies rise 🫶

---

✨ DESCRIPTION ✨

so this whole family of probe points? it exists to probe memory-related events. that's the tea. every single one of them is listed below with its little one-liner and a pointer to the page that spills the full details 💅

---

🦋 vm_fault_contains

test return value for page fault reason. yep, that's the whole job.

see function::vm_fault_contains(3stap) for details.

🦋 vm.pagefault

records that a page fault occurred. it's giving "noted, bestie 📝".

see probe::vm.pagefault(3stap) for details.

🦋 vm.pagefault.return

indicates what type of fault occurred. which flavor of oopsie, exactly.

see probe::vm.pagefault.return(3stap) for details.

🦋 addr_to_node

returns which node a given address belongs to within a NUMA system. NUMA girlies, this one's for you 💜

see function::addr_to_node(3stap) for details.

🦋 vm.write_shared

attempts at writing to a shared page. the audacity, honestly.

see probe::vm.write_shared(3stap) for details.

🦋 vm.write_shared_copy

page copy for shared page write. copy first, write second, no cap.

see probe::vm.write_shared_copy(3stap) for details.

🦋 vm.mmap

fires when an mmap is requested. mmap girlies know 🔥

see probe::vm.mmap(3stap) for details.

🦋 vm.munmap

fires when an munmap is requested.

see probe::vm.munmap(3stap) for details.

🦋 vm.brk

fires when a brk is requested (i.e. the heap will be resized). the heap said "growth era ✨".

see probe::vm.brk(3stap) for details.

🦋 vm.oom_kill

fires when a thread is selected for termination by the OOM killer. it's giving main character elimination arc 💀 rip to that thread fr fr.

see probe::vm.oom_kill(3stap) for details.

🦋 vm.kmalloc

fires when kmalloc is requested.

see probe::vm.kmalloc(3stap) for details.

🦋 vm.kmem_cache_alloc

fires when kmem_cache_alloc is requested.

see probe::vm.kmem_cache_alloc(3stap) for details.

🦋 vm.kmalloc_node

fires when kmalloc_node is requested.

see probe::vm.kmalloc_node(3stap) for details.

🦋 vm.kmem_cache_alloc_node

fires when kmem_cache_alloc_node is requested.

see probe::vm.kmem_cache_alloc_node(3stap) for details.

🦋 vm.kfree

fires when kfree is requested. freeing the memory, releasing the baggage, therapy arc 🌈

see probe::vm.kfree(3stap) for details.

🦋 vm.kmem_cache_free

fires when kmem_cache_free is requested.

see probe::vm.kmem_cache_free(3stap) for details.

---

👑 SEE ALSO 👑

the whole group chat, no one left out:

• function::vm_fault_contains(3stap)
• function::addr_to_node(3stap)
• probe::vm.pagefault(3stap)
• probe::vm.pagefault.return(3stap)
• probe::vm.write_shared(3stap)
• probe::vm.write_shared_copy(3stap)
• probe::vm.mmap(3stap)
• probe::vm.munmap(3stap)
• probe::vm.brk(3stap)
• probe::vm.oom_kill(3stap)
• probe::vm.kmalloc(3stap)
• probe::vm.kmem_cache_alloc(3stap)
• probe::vm.kmalloc_node(3stap)
• probe::vm.kmem_cache_alloc_node(3stap)
• probe::vm.kfree(3stap)
• probe::vm.kmem_cache_free(3stap)
• stap(1)
• stapprobes(3stap)

---

okay that's the whole page, you ate it 💅 this was the SystemTap Tapset Reference, dated September 2026, and yes it's the TAPSET::MEMORY(3stap) era — iconic, no notes, go read stapprobes(3stap) next bestie 🎀✨