STRUCT HTE_TS_INFO(9)
π 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 thexlatecallback 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 whentcbis specified. notcb, 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:
struct hte_device(9)hte_ts_put(9)hte_disable_ts(9)hte_enable_ts(9)of_hte_req_count(9)hte_ts_get(9)hte_request_ts_ns(9)devm_hte_request_ts_ns(9)hte_init_line_attr(9)hte_get_clk_src_info(9)hte_push_ts_ns(9)devm_hte_register_chip(9)
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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms