viortc_alarmq_hdlr(9)

💅 NAME 💅

okay so welcome to the viortc_alarmq_hdlr(9) page in the Kernel API Manual 🫶. This function is literally here to process an alarmq used buffer.

viortc_alarmq_hdlr — process an alarmq used buffer

✨ SYNOPSIS ✨

void viortc_alarmq_hdlr (void *token , unsigned int len , struct
       virtqueue *vq , struct viortc_vq *viortc_vq , struct viortc_dev *viortc
       );

🎀 ARGUMENTS 🎀

bestie, here's the cast list for this function 💖:

• token — token identifying the buffer
• len — bytes written by device
• vq — virtqueue
• viortc_vq — device specific data for virtqueue
• viortc — device data

🦋 DESCRIPTION 🦋

So what's the actual vibe? It processes a VIRTIO_RTC_NOTIF_ALARM notification by calling the RTC class driver. Then it makes the buffer available again. That's the whole glow-up 🌟.

🌸 CONTEXT 🌸

This one runs in virtqueue callback context. That's the setting, bestie — virtqueue callback, no cap.

🌈 SEE ALSO 🌈

The kernel file is ./drivers/virtio/virtio_rtc_driver.c, and the whole friend group is: 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_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_probe(9), viortc_remove(9) 🦋

later, bestie 💖 — this page is viortc_alarmq_hdlr(9) from ./drivers/virtio, dated October 2026. mwah 🫶