viortc_read(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… viortc_read(9) β€” like, the gen-z field guide to the Kernel API Manual, bestie πŸŽ€

okay so. picture this: you're deep in the kernel, you need a clock reading pulled out of a virtio_rtc device, and you do NOT wanna hand-roll the whole request yourself. enter viortc_read β€” it's literally the VIRTIO_RTC_REQ_READ wrapper. that's the whole vibe. it wraps, you read, everyone slays. ✨


✨ NAME ✨

viortc_read β€” the VIRTIO_RTC_REQ_READ wrapper, no cap 🫢


🌸 SYNOPSIS 🌸

int viortc_read (struct viortc_dev *viortc , u16 vio_clk_id , u64
*reading );

yep, that's the signature, character-for-character, don't @ me πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • viortc β€” the device data. like, which virtio_rtc device are we even talking to, bestie? this one. πŸ‘‘
  • vio_clk_id β€” the virtio_rtc clock id, u16 flavoured. it's giving "which clock tho" energy. ⏰
  • reading β€” the clock reading, in [ns]. nanoseconds, iconically. this is where the answer lands. 🎯

πŸ’œ CONTEXT πŸ’œ

Process context. that's it, that's the whole context section. no interrupt-drama, no atomic shenanigans, just process context and good vibes. 🧚


⭐ RETURN ⭐

Zero on success ✨ β€” and a negative error code otherwise 😭. that's the deal, fr fr.


🌈 SEE ALSO 🌈

okay this list is LONG and honestly kind of iconic, so buckle up, we're going down the whole rabbit hole together:

like i said. LONG. but every single one of them is there, and that's on periodt. πŸ’…πŸ”₯


πŸ’– quick vibe check bestie: this one lives under ./drivers/virtio, the manual page is dated October 2026, and it's filed as viortc_read(9). go forth and read some clocks, you absolute main character πŸ«Άβœ¨πŸŽ€
πŸ“¦ where this page comes from