viortc_requestq_hdlr(9)

💅 viortc_requestq_hdlr

okay so bestie, welcome to the Kernel API Manual ✨ this page is literally all about viortc_requestq_hdlr, the requestq used-buffer handler. no cap, it's short and sweet, but we're covering every crumb 🍓

💖 NAME 💖

viortc_requestq_hdlr — process a requestq used buffer 💫

✨ SYNOPSIS ✨

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

the return type is void, so it's not handing anything back — it just does its little handler moment 🫶

🎀 ARGUMENTS 🎀

• token — token identifying the buffer 🏷️
• len — bytes written by device 📏
• vq — virtqueue 🌀
• viortc_vq — device specific data for virtqueue 🎛️
• viortc — device data 🧸

🦋 DESCRIPTION 🦋

Signals completion for each received message. that's the whole vibe, and honestly? iconic 💌

🌸 CONTEXT 🌸

virtqueue callback 🎧

🔥 SEE ALSO 🔥

okay bestie, the friend group is huge — here's the full SEE ALSO squad, nobody left behind 👑

• 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_do_cb(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)

xoxo, your ./drivers/virtio source girlies, dated October 2026 — page viortc_requestq_hdlr(9) signing off 💅✨