ring_buffer_..._disable_cpu(9)

📦 version 7.3.1, in nixpkgs unstable

💅 ring_buffer_..._disable_cpu(9) — like, the Kernel API Manual, bestie ✨

okay so before we even start: yes, the page title is literally ring_buffer_..._disable_cpu(9) (the ... is doing a lot of heavy lifting, iykyk), and it lives in the Kernel API Manual. she's a kernel function, she's fancy, she's about to tell one specific CPU to shut up and stop writing. let's get into it 🎀

🌸 NAME 🌸

ring_buffer_record_disable_cpu — stop all writes into the cpu_buffer 💅

like, all of them. not a vibe check, an actual stop.

✨ SYNOPSIS ✨

void ring_buffer_record_disable_cpu (struct trace_buffer *buffer , int
cpu );

that's it. that's the whole signature. void return, so she gives you nothing back — she just does the thing. iconic behavior honestly 👑

🦋 ARGUMENTS 🦋

  • buffer — the ring buffer you want to stop writes to. she's the main character here, the big one, the whole trace buffer. 🫶
  • cpu — the CPU buffer to stop. yes, specifically that CPU. we're being surgical, not messy. 💅

💖 DESCRIPTION 💖

so here's the tea, bestie: this function prevents all writes to the buffer. every single one. gone. blocked. no cap.

and if something tries to write to the buffer after this? it will fail and return NULL. 😭 that's it, that's the whole attempt, straight to NULL jail.

⚠️ important caller homework: the caller should call synchronize_rcu after this. don't skip it. it's not optional-vibes, it's the actual instruction. 🧚

🎀 SEE ALSO 🎀

the source of all this wisdom lives in the kernel file ./kernel/trace/ring_buffer.c ⭐ — and here's the full friend group, every single one of them, in the original order:

and that's the whole page, bestie 💜 she comes to you straight from ./kernel/trace, dated October 2026, and yes the docs really did name the footer file and the month like that — periodt. go call synchronize_rcu, ily, bye 🦋🌸

📦 where this page comes from