viortc_do_cb(9)

💖 viortc_do_cb — generic virtqueue callback logic 💖

okay bestie, welcome to the viortc_do_cb(9) page from the Kernel API Manual — this is the generic virtqueue callback logic, and it's giving main-character callback energy ✨

---

🌸 NAME 🌸

viortc_do_cb — generic virtqueue callback logic

---

✨ SYNOPSIS ✨

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

---

🎀 ARGUMENTS 🎀

• vq — virtqueue. literally the virtqueue in question 💅
• handle_buf — function to process a used buffer. it's the callback bestie, it handles the buffer, periodt 🫶

---

🦋 CONTEXT 🦋

This is virtqueue callback territory — typically interrupt. It takes and releases the vq lock, okay? Takes it, releases it, handles its business 😌🔒

---

🌈 SEE ALSO 🌈

the whole icon squad is here, no cap:

• Kernel file ./drivers/virtio/virtio_rtc_driver.c
• 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_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_probe(9)
• viortc_remove(9)

---

byeee, this little icon was brought to you by source ./drivers/virtio 🌟, dated October 2026, and the page itself is viortc_do_cb(9) — mwah 💋✨