PROBE::VM.WRITE_SH(3stap)

πŸ’– probe::vm.write_shared_copy β€” the other write_shared probe πŸ’–

okay bestie, welcome to the SystemTap Tapset Reference β€” this page is PROBE::VM.WRITE_SH(3stap) and it's lowkey one of the most underrated little tapsets in the memory crew. let's get into it 🫢


✨ NAME ✨

probe::vm.write_shared_copy β€” page copy for shared page write

like... it's literally the moment a shared page has to get copied before you can write to it. it's giving copy-on-write main character energy πŸ‘‘


🌸 SYNOPSIS 🌸

probe vm.write_shared_copy {}

no arguments, no fuss, just vibes and a probe point πŸ’…


πŸŽ€ VALUES πŸŽ€

the tea this probe hands you when it fires:

  • address β€” the address of the shared write. that's the spot. that's where the action is happening πŸ“
  • zero β€” a boolean telling you whether it's a zero page, which means you can do a clear instead of a copy. frugal. efficient. we love to see it ✨
  • name β€” name of the probe point. it's the label on the box, bestie 🏷️

πŸ¦‹ CONTEXT πŸ¦‹

the process attempting the write. yeah. that one. the one doing the writing. it's always the one you least expect πŸ™ˆ


πŸ’œ DESCRIPTION πŸ’œ

so here's the lore: this probe fires when a write to a shared page requires a page copy. and it is always preceded by a vm.write_shared β€” like, it never shows up alone, it's a package deal, they arrive together, one right after the other, fr fr 🧚


πŸ”₯ SEE ALSO πŸ”₯


ngl if you're tracing shared-page writes, this probe is the one that tells you "okay we had to actually duplicate the page" β€” which is exactly the kind of thing you want to know when you're staring at a perf number wondering why it's so big πŸ’€

and that's the whole page!! tysm for reading, go trace something cool, i'm obsessed with you πŸ’–

β€” with love, your friendly neighborhood tapset, from the SystemTap Tapset Reference, September 2026 πŸŒˆπŸŽ€

πŸ“¦ where this page comes from