ring_buffer...d_enable_cpu(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ring_buffer_record_enable_cpu β€” Kernel API Manual ✨

okay so bestie, welcome to the page for ring_buffer_record_enable_cpu(9). yes that's the whole name, it's long, it's giving "my parents gave me a full government name" energy, but we move. this is the Kernel API Manual page, and honestly? it's a short one. lowkey iconic of it.


🌸 NAME 🌸

ring_buffer_record_enable_cpu β€” enable writes to the buffer

that's it. that's the job. it turns the writing back ON for one little CPU. slay.


πŸ¦‹ SYNOPSIS πŸ¦‹

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

yes she's void, she returns nothing, she's not here to give you feedback, she's here to do the thing. main character energy fr fr.


πŸŽ€ ARGUMENTS πŸŽ€

so there's two of them, and no there is no third one, don't come for me:

  • buffer β€” the ring buffer you wanna enable writes on. that's your girl. you're giving her permission to be written to again πŸ’–
  • cpu β€” the CPU to enable. just the one. one CPU. specifically that one. not all of them, don't be greedy πŸ™ˆ

⭐ DESCRIPTION ⭐

okay this is the important bit so listen up. multiple disables will need the same number of enables to truly enable the writing (much like preempt_disable).

read that again, bestie. it's a counter situation, not a light switch. if you disabled three times, you gotta enable three times to actually get writing back. it's not one-and-done. it's giving ✨ commitment ✨. and yeah, the manpage literally compares it to preempt_disable β€” that's the vibe, that's the reference, iykyk πŸ’€

so like… if you're sitting there wondering "why is my buffer still not recording, i literally called enable" β€” did you disable it more than once? bestie. count. πŸ”₯

πŸ’œ SEE ALSO πŸ’œ

okay this is the part where the page just… goes off. it's a whole friend group, a whole group chat, everyone's invited. bring snacks πŸ“

kernel file ./kernel/trace/ring_buffer.c β€” and then, in order, because i'm not about to rearrange her:

like i said. everyone is here. it's a reunion 🫢


and that's the whole page!! short, sweet, and yes, you do have to match your enables to your disables. no cap. πŸ’…

sign-off time: this little masterpiece lives in <purple>./kernel/trace</purple>, it's dated October 2026, and its version-y header vibe is <lavender>ring_buffer...d_enable_cpu(9)</lavender> β€” yes they truncated the name in the footer, she's mysterious like that 😭. bye bestie, go enable some writes πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from