viortc_probe(9)

viortc_probe(9) ✨

okay so bestie, this is the viortc_probe(9) page from the Kernel API Manual — it's all about probing a virtio_rtc virtio device. no cap, that's the whole mission. 🫶

---

🌸 NAME 🌸

viortc_probe — probe a virtio_rtc virtio device. literally its entire personality. 💅

✨ SYNOPSIS ✨

int viortc_probe (struct virtio_device *vdev );

copy that exactly, spaces and all — the signature is the signature, bestie. 🎀

🧚 ARGUMENTS 🧚

• vdev — the virtio device. that's the one being handed over. 🦋

🌈 CONTEXT 🌈

Process context. that's the vibe check: process context. 🫧

⭐ RETURN ⭐

• Zero on success. slay. ✅
• Negative error code otherwise. so if it's not zero, it's a negative error code, periodt. 💀

👑 SEE ALSO 👑

Kernel file: ./drivers/virtio/virtio_rtc_driver.c — that's the file the page points at. 📁

Here's the whole friend group, all of them, no skips:

• struct viortc_vq(9)
• struct viortc_dev(9)
• struct viortc_msg(9)
• viortc_class_from_dev(9)
• viortc_alarms_supported(9)
• viortc_feed_vq(9)
• viortc_msg_init(9)
• viortc_msg_release(9)
• viortc_do_cb(9)
• viortc_requestq_hdlr(9)
• viortc_cb_requestq(9)
• viortc_alarmq_hdlr(9)
• viortc_cb_alarmq(9)
• viortc_get_resp_errno(9)
• viortc_msg_xfer(9)
• VIORTC_DECLARE_MSG_HDL_ONSTACK(9)
• VIORTC_MSG(9)
• VIORTC_MSG_INIT(9)
• VIORTC_MSG_WRITE(9)
• VIORTC_MSG_READ(9)
• viortc_read(9)
• viortc_read_cross(9)
• viortc_cfg(9)
• viortc_clock_cap(9)
• viortc_cross_cap(9)
• viortc_read_alarm(9)
• viortc_set_alarm(9)
• viortc_set_alarm_enabled(9)
• viortc_init_rtc_class_clock(9)
• viortc_init_ptp_clock(9)
• viortc_init_clock(9)
• viortc_clocks_deinit(9)
• viortc_clocks_init(9)
• viortc_populate_vq(9)
• viortc_alloc_vq_bufs(9)
• viortc_init_vqs(9)
• viortc_remove(9)

go read these too, iykyk. 🔥

mwah 💖 — signing off from ./drivers/virtio, dated October 2026.