viortc_init_vqs(9)

💖 NAME 💖

okay bestie, this is viortc_init_vqs(9) from the Kernel API Manual, and the name is literally viortc_init_vqs — init virtqueues. She's the main character of virtqueue setup, no cap.

✨ SYNOPSIS ✨

int viortc_init_vqs (struct viortc_dev *viortc );

🎀 ARGUMENTS 🎀

• viortc — device data. That's it, bestie; the argument is the device data and we move.

🦋 DESCRIPTION 🦋

viortc_init_vqs inits virtqueues and associated data. That's the entire description — she's giving setup energy, and the associated data comes along for the ride. Obsessed with a concise icon.

🌸 CONTEXT 🌸

Process context. Periodt — that's the context you're in.

🔥 RETURN 🔥

• Zero on success. Slay.
• Negative error code otherwise. If it's negative, it's not giving success, okay?

👑 SEE ALSO 👑

the whole squad:

• 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_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_probe(9)
• viortc_remove(9)

okay that's the page, bestie 💅 this one comes from ./drivers/virtio and is dated October 2026 — mwah, bye 🫶