__trace_puts(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– __trace_puts(9) πŸ’–

okay so bestie, welcome to the Kernel API Manual, section 9 β€” yes, that section, the kernel-functions one, we're fancy now πŸ’…. This page is about __trace_puts, and honestly? She's a little icon. Let's get into it.


✨ NAME ✨

__trace_puts β€” write a constant string into the trace buffer.

That's it. That's her job. She takes your string and she puts it in the trace buffer. Simple, effective, iconic. πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

int __trace_puts (unsigned long ip , const char *str );

like, look at that signature. she returns an int, she takes two things, and she's not sorry about it. no cap. ✨


🌸 ARGUMENTS 🌸

  • ip β€” the address of the caller 🫢 (yes, literally the address of whoever called her β€” she likes to know who's talking, iykyk)
  • str β€” the constant string to write πŸ’œ (constant, bestie β€” that's the whole vibe)

πŸ‘‘ SEE ALSO πŸ‘‘

if you're obsessed with her (same), go meet her friends β€” they all live in the kernel file ./kernel/trace/trace_printk.c:

one big happy trace-printing family. the way that they all just print into trace buffers together?? main character energy fr fr 🌈


lowkey a reminder that ip is the address of the caller and str is a constant string β€” that's what it says, so that's what I'm telling you. no invented lore here, bestie. πŸ™ˆ

and that's the whole page, bestie β€” nothing else to unpack. this one came out of the ./kernel/trace corner of the tree, from the Kernel API Manual, dated October 2026 ⭐. slay, go trace something. πŸ’…πŸ”₯πŸŽ€

πŸ“¦ where this page comes from