update_max_tr(9)

💖 NAME 💖

okay so bestie, welcome to the Kernel API Manual page for update_max_tr(9) — and the whole vibe is literally: update_max_tr — snapshot all trace buffers from global_trace to max_tr. 🦋✨

🎀 SYNOPSIS 🎀

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

🌸 ARGUMENTS 🌸

• tr — tracer 👑
• tsk — the task with the latency 😭
• cpu — The cpu that initiated the trace. 💻
• cond_data — User data associated with a conditional snapshot 🙈

✨ DESCRIPTION ✨

So what it does: flip the buffers between tr and max_tr, and record information about which task was the cause of this latency. That’s the whole tea ☕💅 — buffer flip + info about the task that caused the latency, iconic fr fr.

🔥 SEE ALSO 🔥

Kernel file ./kernel/trace/trace_snapshot.c, plus these besties:

• 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_single(9)

byeee 🫶 this page comes from ./kernel/trace, dated October 2026, and it’s update_max_tr(9) — mwah, ty for reading! 💜🌈