enqueue_ddcb(9)

💅 enqueue_ddcb(9) — Kernel API Manual 💅

🎀 NAME 🎀

enqueue_ddcb — Enqueue a DDCB ✨

✨ SYNOPSIS ✨

int enqueue_ddcb (struct genwqe_dev *cd , struct ddcb_queue *queue ,
struct ddcb *pddcb , int ddcb_no );

🫶 ARGUMENTS 🫶

• cd — pointer to the genwqe device descriptor; it’s giving main-character device energy 👑
• queue — the queue this operation should be done on 💅
• pddcb — pointer to the ddcb structure 🦋
• ddcb_no — pointer to the ddcb number being tapped 👀

🌸 DESCRIPTION 🌸

Okay so this function starts execution of a DDCB by tapping it, or appends it to the queue via the NEXT bit. It does that with an atomic "compare and swap" instruction and by checking SHI and HSI of the previous DDCB. No cap. ✨

⚠️ This function must only be called with ddcb_lock held. Like, for real, bestie — do not skip that lock. 💀

🔥 RETURN 🔥

• 1 — if new DDCB is appended to previous
• 2 — if DDCB queue is tapped via register/simulation

🦋 SEE ALSO 🦋

Kernel file: ./drivers/misc/genwqe/card_ddcb.c — and here’s the whole squad:

• genwqe_crc16(9)
• ddcb_requ_finished(9)
• copy_ddcb_results(9)
• genwqe_check_ddcb_queue(9)
• __genwqe_wait_ddcb(9)
• get_next_ddcb(9)
• __genwqe_purge_ddcb(9)
• __genwqe_enqueue_ddcb(9)
• __genwqe_execute_raw_ddcb(9)
• genwqe_next_ddcb_ready(9)
• genwqe_ddcbs_in_flight(9)
• genwqe_card_thread(9)
• genwqe_setup_service_layer(9)
• queue_wake_up_all(9)
• genwqe_finish_queue(9)
• genwqe_release_service_layer(9)

💌 okay that’s the page, bestie — source/version is ./drivers/misc/genwqe, date is October 2026, and the manual page is enqueue_ddcb(9). mwah, go enqueue something cute 💋