STRUCT PFRT_LOG_DATA_INFO(9)
π struct pfrt_log_data_info(9) π
okay bestie so this is a page from the Kernel API Manual, section 9, and it's all about struct pfrt_log_data_info β literally just the Log Data from the telemetry service. that's it, that's the whole vibe. π
β¨ NAME β¨
struct pfrt_log_data_info β Log Data from telemetry service. periodt. π
π¦ SYNOPSIS π¦
here's the struct in all its glory, copy it exactly, no cap:
struct pfrt_log_data_info {
__u32 status;
__u32 ext_status;
__u64 chunk1_addr_lo;
__u64 chunk1_addr_hi;
__u64 chunk2_addr_lo;
__u64 chunk2_addr_hi;
__u32 max_data_size;
__u32 chunk1_size;
__u32 chunk2_size;
__u32 rollover_cnt;
__u32 reset_cnt;
};
π Members π
okay now the member-by-member breakdown, and yes we're doing all eleven, no skipping, the way that attention to detail is iconic:
statusβ your little indicator of whether this update actually succeeded. vibe check for the update. β¨ext_statusβ the implementation specific update result. so like, the details are up to whoever implemented it, iykyk.chunk1_addr_loβ the Low 32bit physical address of the telemetry data chunk1 starting address. πchunk1_addr_hiβ the High 32bit physical address of the telemetry data chunk1 starting address. two halves, one address, we love a duo. π«Άchunk2_addr_loβ the Low 32bit physical address of the telemetry data chunk2 starting address. πchunk2_addr_hiβ the High 32bit physical address of the telemetry data chunk2 starting address. matching set fr fr. πΈmax_data_sizeβ the Maximum supported size of data of all data chunks combined. as in, everything together, the whole squad. π₯chunk1_sizeβ Data size in bytes of the telemetry data chunk1 buffer. bytes, bestie, bytes. πchunk2_sizeβ Data size in bytes of the telemetry data chunk2 buffer. same energy, different chunk. π§rollover_cntβ Number of times telemetry data buffer is overwritten since telemetry buffer reset. it's counting the overwrites. lowkey dramatic. πreset_cntβ Number of times telemetry services resets that results in rollover count and data chunk buffers are reset. so a reset here wipes the rollover count and the chunk buffers, that's the whole deal. π
π SEE ALSO π
go read these next, bestie, they're literally all connected β Kernel file ./include/uapi/linux/pfrut.h:
PFRU_IOC_SET_REV(9)PFRU_IOC_STAGE(9)PFRU_IOC_ACTIVATE(9)PFRU_IOC_STAGE_ACTIVATE(9)PFRU_IOC_QUERY_CAP(9)struct pfru_payload_hdr(9)struct pfru_update_cap_info(9)struct pfru_com_buf_info(9)struct pfru_updated_result(9)struct pfrt_log_info(9)PFRT_LOG_IOC_SET_INFO(9)PFRT_LOG_IOC_GET_INFO(9)PFRT_LOG_IOC_GET_DATA_INFO(9)
and that's the whole page, bestie π«Ά sign-off time: this one lives over in ./include/uapi/linux, dated October 2026, and it's filed under struct pfrt_log_data_info(9). slay. πβ¨
π¦ 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