trace_print_bitmask_seq(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ¦‹ NAME πŸ¦‹

trace_print_bitmask_seq β€” print a bitmask to a sequence buffer

okay so welcome to the trace_print_bitmask_seq(9) page from the Kernel API Manual, bestie πŸ’– you're gonna eat this one up.


πŸŽ€ SYNOPSIS πŸŽ€

Here's the signature, exactly as it appears β€” no cap:

const char * trace_print_bitmask_seq (struct trace_iterator *iter , void *bitmask_ptr , unsigned int bitmask_size );

πŸ’… ARGUMENTS πŸ’…

Three little arguments, all doing main character work:

  • iter β€” the trace iterator for the current event instance.
  • bitmask_ptr β€” the pointer to the bitmask data.
  • bitmask_size β€” the size of the bitmask in bytes.

πŸ”₯ DESCRIPTION πŸ”₯

So the vibe is: this function prints a bitmask into a sequence buffer as either a hex string or a human-readable range list, depending on the instance's "bitmask-list" trace option. Slay πŸ’…

Not me formatting the bitmask into the iterator's temporary scratchpad rather than the primary sequence buffer β€” that's literally the move 😭. It avoids duplication and pointer-collision issues when the returned string is processed by a "s" specifier in a TP_printk macro. Obsessed.

the returned string lives in the temporary buffer, not the primary sequence buffer β€” iykyk πŸ’–

Returns a pointer to the formatted string within the temporary buffer. Periodt ✨


🌈 SEE ALSO 🌈

Kernel file ./kernel/trace/trace_output.c β€” and the whole friend group is trace_print_hex_seq(9), trace_print_lat_fmt(9), ftrace_find_event(9), register_trace_event(9), unregister_trace_event(9).


cute sign-off: source/version ./kernel/trace, date October 2026 πŸ’–βœ¨

πŸ“¦ where this page comes from