tracing_snap..._cond_enable(9)

💖 NAME 💖

okay so bestie, welcome to the tracing_snap..._cond_enable(9) page from the Kernel API Manual ✨ this is the function that's literally here to enable conditional snapshot for an instance — main character energy fr fr 👑

tracing_snapshot_cond_enable — enable conditional snapshot for an instance. That's the whole name-and-job situation 💅

---

✨ SYNOPSIS ✨

the signature is giving:

int tracing_snapshot_cond_enable (struct trace_array *tr , void
       *cond_data , cond_update_fn_t update );

---

🎀 ARGUMENTS 🎀

• tr — the tracing instance. You know, the one getting the conditional snapshot treatment 👑
• cond_data — user data to associate with the snapshot. Your little data bestie for the snapshot 🫶
• update — implementation of the cond_snapshot update function. Yes, the actual update function doing the work 💅

---

🦋 DESCRIPTION 🦋

okay so here's the lore: it checks whether the conditional snapshot for the given instance has already been enabled, or whether the current tracer is already using a snapshot. If either one is a yes, it returns -EBUSY — and yeah, that's the busy signal doing its thing 💀 no cap.

If not, it creates a cond_snapshot and saves the cond_data and the update function inside. It returns 0 if successful, and error otherwise. So 0 is the slay outcome, and anything else is the error vibe check failing 😭

---

🌈 SEE ALSO 🌈

• Kernel file ./kernel/trace/trace_snapshot.c — the source file in question, go say hi 🦋
• tracing_snapshot_cond(9)
• tracing_cond_snapshot_data(9)
• tracing_snapshot_alloc(9)
• tracing_snapshot_cond_disable(9)
• update_max_tr(9)
• update_max_tr_single(9)

---

cute little sign-off 🎀 source/version: ./kernel/trace · date: October 2026 · page: tracing_snap..._cond_enable(9) — bye bestie, go be iconic with those conditional snapshots 💖🎀✨