telemetry_read_events(9)

💅 telemetry_read_events(9) — from the Kernel API Manual, bestie

okay so picture this: you're deep in the kernel, you want telemetry samples, and this function is literally the girl who goes and gets them for you. no cap. it's telemetry_read_events, and it's giving main character energy in the telemetry department. ✨

---

🌸 SYNOPSIS 🌸

int telemetry_read_events (enum telemetry_unit telem_unit , struct
       telemetry_evtlog *evtlog , int len );

it returns an int, bestie. that's the vibe check right there. 🫶

---

🎀 ARGUMENTS 🎀

• telem_unit — tells the function which one you want: IOSS or PSS Read. pick your fighter, babes 💅
• evtlog — an array of telemetry_evtlog structs that the function fills with data. the way it knows what to read? evtlog.telem_evt_id specifies the ids. iconic behavior honestly 🔥
• len — the length of the array of evtlog. it's literally just how many slots you're handing over, no more no less 🎀

---

⭐ RETURN ⭐

it returns the number of eventlogs read on success. and < 0 on failure — so if you see a negative number, that's your sign something went off and you should go touch grass and check your args 😭💀

fr fr: success = count of eventlogs, failure = anything below zero. don't get it twisted 🫶

---

🦋 SEE ALSO 🦋

• the kernel file itself, living its best life at ./drivers/platform/x86/intel/telemetry/core.c 📁
• telemetry_read_eventlog(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)

the whole telemetry friend group, honestly. go say hi to all of them 💜

---

and that's the page!! this one's from the ./drivers/platform/x86/intel/t... corner of the tree, dated October 2026, and it's telemetry_read_events(9) — go read some events, bestie, you've got this 💖🌈✨