STRUCT HTE_TS_INFO(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct hte_ts_info(9)

okay so bestie, welcome to the Kernel API Manual β€” this is struct hte_ts_info(9)</p> and it's literally the whole personality file for "information related to requested timestamp." yes that's the actual NAME, no cap. it's giving timestamp main character energy πŸ‘‘


✨ NAME ✨

struct hte_ts_info β€” Information related to requested timestamp. that's it, that's the vibe. it holds the tea about a timestamp you asked for 🫢


πŸ¦‹ SYNOPSIS πŸ¦‹

here's the whole struct, copy it exactly pls, don't touch a single character:

struct hte_ts_info {
    u32 xlated_id;
    unsigned long flags;
    unsigned long hte_cb_flags;
    u64 seq;
    char *line_name;
    bool free_attr_name;
    hte_ts_cb_t cb;
    hte_ts_sec_cb_t tcb;
    atomic_t dropped_ts;
    spinlock_t slock;
    struct work_struct cb_work;
    struct mutex req_mlock;
    struct dentry *ts_dbg_root;
    struct hte_device *gdev;
    void *cl_data;
 };

like look at her. fifteen fields. absolute queen behavior πŸ‘‘


🌸 Members 🌸

let's go field by field, i got you:

  • xlated_id β€” the Timestamp ID as understood between the HTE subsys and the HTE provider. See the xlate callback API. iykyk πŸ”₯
  • flags β€” Flags holding state information. state? held. πŸ’…
  • hte_cb_flags β€” Callback related flags. callback flags doing callback things ✨
  • seq β€” Timestamp sequence counter. counting, but make it timestamps πŸ”’
  • line_name β€” the HTE allocated line name. she was named by HTE herself πŸŽ€
  • free_attr_name β€” If set, free the attr name. so like, only free it when this is set, ok? don't be out here freeing things uninvited πŸ™ˆ
  • cb β€” A nonsleeping callback function provided by clients. emphASIS on nonsleeping β€” this one does not nap 😴🚫
  • tcb β€” A secondary sleeping callback function provided by clients. this one DOES nap, she's the secondary, she's chill πŸŒ™
  • dropped_ts β€” Dropped timestamps. rip to those timestamps, they're with the angels now πŸ’€
  • slock β€” Spin lock to synchronize between disable/enable, request/release APIs. she keeps the peace 🧚
  • cb_work β€” callback workqueue, used when tcb is specified. no tcb, no workqueue, simple as that πŸ“
  • req_mlock β€” Lock during timestamp request/release APIs. mutual exclusion but make it timestamp requests πŸ”
  • ts_dbg_root β€” Root for the debug fs. debugfs lives here, respectfully πŸ›
  • gdev β€” HTE abstract device that this timestamp information belongs to. every timestamp info has a home device, periodt 🏠
  • cl_data β€” Client specific data. client's data, client's business πŸ’œ

πŸ‘‘ SEE ALSO πŸ‘‘

go read these next bestie, they're all in the kernel file ./drivers/hte/hte.c:


ok that's the whole page, every single field accounted for, nothing skipped, we ate and left no crumbs 🍽️✨

🌈 byeee 🌈 this came out of ./drivers/hte, dated October 2026, and it's the struct hte_ts_info(9) page β€” mwah, slay, go request some timestamps bestie πŸ’–πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from