tracing_snapshot_cond(9)

💖 NAME 💖

okay so bestie, meet tracing_snapshot_cond(9) from the Kernel API Manual — the iconique “conditionally take a snapshot of the current buffer” function. no cap, it’s the conditional cousin of the snapshot game. 🦋

✨ SYNOPSIS ✨

void tracing_snapshot_cond (struct trace_array *tr , void *cond_data );

🎀 ARGUMENTS 🎀

• tr — the tracing instance you’re snapshotting, bestie. that’s the trace array in question. 💅
• cond_data — the data that gets tested conditionally and possibly saved. it’s giving “the vibe check payload” 🫶

🔥 DESCRIPTION 🔥

okay so this is literally the same as tracing_snapshot except the snapshot is conditional — the snapshot will only happen if the cond_snapshot.update implementation receiving the cond_data returns true. that means the trace array’s cond_snapshot update operation used the cond_data to determine whether the snapshot should be taken, and if it was, presumably saved it along with the snapshot. periodt. 💖

conditional means conditional, bestie: that update implementation has to return true for the snapshot to happen. 🌸

🌈 SEE ALSO 🌈

• Kernel file ./kernel/trace/trace_snapshot.c
• tracing_cond_snapshot_data(9), tracing_snapshot_alloc(9), tracing_snapshot_cond_enable(9), tracing_snapshot_cond_disable(9), update_max_tr(9), update_max_tr_single(9)

mwah 💋 — source/version: ./kernel/trace, dated October 2026. go take that conditional snapshot, bestie. 👑