VIORTC_DECLA..._HDL_ONSTACK(9)

okay bestie, welcome to the VIORTC_DECLA..._HDL_ONSTACK(9) page from the Kernel API Manual ✨ this is the one about declaring a message handle on the stack, and we’re gonna get you comfy with it.

🌸 NAME 🌸

VIORTC_DECLARE_MSG_HDL_ONSTACK — declare message handle on stack 💅

Literally what it says: declare a message handle on the stack. That’s the whole vibe. The macro name is long enough to need its own zip code, but the job is straightforward.

✨ SYNOPSIS ✨

VIORTC_DECLARE_MSG_HDL_ONSTACK (hdl , msg_id , msg_req , msg_resp );

Call it with the four args below and you’re slaying 🫶

🎀 ARGUMENTS 🎀

Here are the four cuties this macro expects, in order:

• hdl — message handle name 🌟
• msg_id — message type id 🆔
• msg_req — message request type 📨
• msg_resp — message response type 💌

🦋 SEE ALSO 🦋

If you wanna spiral into the virtio/rtc cinematic universe, these are the linked pages and the kernel file to check, 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_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_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)

mwah 💋 that’s the whole page, bestie. Source/version/date corner: ./drivers/virtio — October 2026 — VIORTC_DECLA..._HDL_ONSTACK(9). Go declare that message handle on the stack and slay ✨