update_max_tr_single(9)

💅 update_max_tr_single(9) — the Kernel API Manual, bestie edition 🎀

okay so literally welcome to the Kernel API Manual page for update_max_tr_single(9) and honestly? she's a baddie with one very specific job. let's get into it ✨

---

✨ NAME ✨

update_max_tr_single — only copy one trace over, and reset the rest 🫶

like... one (1) trace gets the copy treatment and everybody else gets wiped. no cap.

---

🌸 SYNOPSIS 🌸

void update_max_tr_single (struct trace_array *tr , struct task_struct *tsk , int cpu );

return type is void, so she gives you nothing back, she just does things. main character energy fr 💅

---

🦋 ARGUMENTS 🦋

• tr — the tracer. that's the struct trace_array * bestie herself 💖
• tsk — the task with the latency 👀 (the whole reason we're here)
• cpu — the cpu of the buffer to copy. just the one. we're being selective 🎯

---

⭐ DESCRIPTION ⭐

Flip the trace of a single CPU buffer between the tr and the max_tr.

that's it, that's the whole vibe. one CPU buffer, two homes (tr and max_tr), and she's flipping it between them like a light switch 🧚✨

---

🔥 SEE ALSO 🔥

• Kernel file ./kernel/trace/trace_snapshot.c — go read the source, iykyk 📖
• tracing_snapshot_cond(9)
• tracing_cond_snapshot_data(9)
• tracing_snapshot_alloc(9)
• tracing_snapshot_cond_enable(9)
• tracing_snapshot_cond_disable(9)
• update_max_tr(9) — her sibling, the plural one 💀

---

and that's the page!! mwah 💋 this came straight out of ./kernel/trace, dated October 2026, and it's update_max_tr_single(9) signing off — slay, bye, go flip some buffers 🌈👑