STRUCT PFRT_LOG_DATA_INFO(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– 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:


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