instrument_a...c_read_write(9)

📦 version 7.3.1, in nixpkgs unstable

💅 instrument_atomic_read_write(9) — from the Kernel API Manual, bestie 🎀

okay so real talk, this one is short but it matters, and it lives in the instrument_a...c_read_write(9) corner of the kernel docs. it's giving "small but crucial", ykwim? let's get into it ✨

✨ NAME ✨

instrument_atomic_read_write — basically it instruments an atomic read-write access 🦋

like, that's the whole vibe check: atomic read-write goes in, gets instrumented. slay.

🌸 SYNOPSIS 🌸

void instrument_atomic_read_write (const volatile void *v , size_t size );

no cap, that's the exact signature — v is a const volatile void * and size is a size_t, and the whole thing returns void because it's out here doing work, not collecting receipts 💅

👑 ARGUMENTS 👑

  • v — the address of the access 📍 like, where the thing is happening
  • size — the size of the access 📏 like, how much of the thing is happening

both iconic, both required, no skips 🫶

💖 DESCRIPTION 💖

okay so listen up, because this part is literally the whole point:

it instruments an atomic read-write access. and here's the detail you absolutely cannot drop — the instrumentation should be inserted before the actual write happens ⭐

read that again, bestie. before. not after, not "whenever you get around to it". before. the ordering is the moment, iykyk 💀

🔥 SEE ALSO 🔥

this is the friend group right here, all living in the kernel file ./include/linux/instrumented.h 💜

literally the whole squad, go say hi 🌈

ngl the ordering thing is the one you'll regret ignoring, so like… don't 🙈

and that's the page! courtesy of ./include/linux, dated October 2026, filed under instrument_a...c_read_write(9) — mwah, go instrument something, you got this 🧚💖✨

📦 where this page comes from