STRUCT ADF_TL_DBG_COUNTER(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ struct adf_tl_dbg_counter(9) β€” the telemetry counter definition glow-up πŸŽ€

Okay bestie, so this is a page from the Kernel API Manual and it's all about struct adf_tl_dbg_counter β€” literally the little struct that defines a telemetry counter. It's giving "small but iconic," no cap. πŸ¦‹


✨ SYNOPSIS ✨

struct adf_tl_dbg_counter {
    const char *name;
    enum adf_tl_counter_type type;
    size_t offset1;
    size_t offset2;
 };

Look at her. Four members. Zero drama. Main character energy fr fr. πŸ’…


🌸 Members 🌸

  • name β€” the name of the counter, aka what gets printed in the report. It's literally the counter's whole identity, bestie β€” this is the string that shows up when the report comes out. 🫢
  • offset1 β€” offset of 1st register. That's the first register's offset, periodt. πŸ“
  • offset2 β€” offset of 2nd optional register. Key word: optional πŸ‘€ β€” she's the second register's offset, and she's not required to show up to the party.
Not me leaving out type β€” okay so the SYNOPSIS lowkey lists enum adf_tl_counter_type type; as a member too, but the original Members section only breaks down name, offset1 and offset2. So that's exactly what I'm giving you. Keeping it 100 with the source. πŸ’―

πŸ‘‘ SEE ALSO πŸ‘‘

Go read those next, iykyk β€” they're the rest of the lore. 🌈


And that's the whole page, babes! This one comes to you from ./drivers/crypto/intel/qat/qat_common/adf_tl_debugfs.h (per that SEE ALSO line), dated October 2026, and it lives right there in the Kernel API Manual. Mwah. πŸ’–βœ¨πŸŽ€πŸŒΈπŸ¦‹πŸ’œ

πŸ“¦ where this page comes from