tracing_snapshot_alloc(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

NAME ✨

okay so bestie, welcome to the Kernel API Manual β€” this page is literally tracing_snapshot_alloc(9), title and all, and it's giving β€œallocate + snapshot” main character energy. πŸ’–

tracing_snapshot_alloc β€” allocate and take a snapshot of the current buffer. πŸ¦‹

SYNOPSIS πŸŽ€

void tracing_snapshot_alloc (void );

ARGUMENTS πŸ’…

  • void β€” no arguments. literally none, bestie, not even a lil one. 🫢

DESCRIPTION 🌸

Okay so this is similar to tracing_snapshot, but it will allocate the snapshot buffer if it isn't already allocated. That's the glow-up: alloc first, snapshot too. ✨

Use this only where it is safe to sleep, as the allocation may sleep. No cap β€” that's the important caveat, so don't ignore it. 😭

This causes a swap between the snapshot buffer and the current live tracing buffer. You can use this to take snapshots of the live trace when some condition is triggered, but continue to trace. It's giving β€œsnapshot and keep it moving” energy. πŸ’…

Sleep-safe zone only, bestie: the allocation may sleep, so use this only where it is safe to sleep. 🫢

SEE ALSO πŸ¦‹


k bye bestie πŸ’– this iconic page lives at ./kernel/trace, is dated October 2026, and answers to tracing_snapshot_alloc(9). periodt. πŸŽ€

πŸ“¦ where this page comes from