telemetry_read_eventlog(9)
π NAME π
telemetry_read_eventlog β fetch the Telemetry log from PSS or IOSS. This is the Kernel API Manual page for telemetry_read_eventlog(9), and bestie, we are officially in telemetry-read territory π¦β¨
π SYNOPSIS π
int telemetry_read_eventlog (enum telemetry_unit telem_unit , struct
telemetry_evtlog *evtlog , int len );
πΈ ARGUMENTS πΈ
telem_unitβ specify whether this is an IOSS or PSS Read, okay? πevtlogβ array oftelemetry_evtlogstructs to fill data. Itβs the little collection that gets the data, no cap π«Άlenβ length of the array ofevtlog. Literally how many entries youβre working with, bestie β¨
π₯ RETURN π₯
Number of eventlogs read for success, < 0 for failure. So success gives you a count, and failure is giving bad-vibes-negative ππ
π SEE ALSO π
- Kernel file
./drivers/platform/x86/intel/telemetry/core.c telemetry_read_events(9)telemetry_raw_read_eventlog(9)telemetry_get_trace_verbosity(9)telemetry_set_trace_verbosity(9)telemetry_set_pltdata(9)telemetry_clear_pltdata(9)telemetry_get_pltdata(9)telemetry_get_evtname(9)
Signing off from the Kernel API Manual, October 2026 edition, with the source/version line pointing at ./drivers/platform/x86/intel/t... β telemetry_read_eventlog(9) out, periodt π
πβ¨
π¦ 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