viortc_set_alarm(9)

💅 viortc_set_alarm(9) — Kernel API Manual ✨

🎀 NAME 🎀

viortc_set_alarm — the VIRTIO_RTC_REQ_SET_ALARM wrapper. that's the whole assignment, bestie 💖

✨ SYNOPSIS ✨

okay so the call looks exactly like this, no cap:

int viortc_set_alarm (struct viortc_dev *viortc , u16 vio_clk_id , u64 alarm_time , bool alarm_enable );

🌸 ARGUMENTS 🌸

here are the four little besties sliding into this function:

• viortc — device data. literally the device situation.
• vio_clk_id — virtio_rtc clock id. iykyk.
• alarm_time — alarm time in ns. nanoseconds energy ✨
• alarm_enable — enable or disable alarm. the switch vibes, fr fr.

🦋 CONTEXT 🦋

Process context. that's it, that's the vibe check 💅

🔥 RETURN 🔥

Zero on success, negative error code otherwise. periodt. 💅

🌈 SEE ALSO 🌈

the full kernel-lore deep dive starts with Kernel file ./drivers/virtio/virtio_rtc_driver.c, and then the bestie refs are: 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_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_probe(9), viortc_remove(9). go off, queen 👑.

okay bye bestie 🫶 this page is giving ./drivers/virtio energy, dated October 2026, and it's the viortc_set_alarm(9) manual page — mwah 💋