ibmvscsi_init_crq_queue(9)

💖 NAME 💖

Okay bestie, meet ibmvscsi_init_crq_queue — from the Kernel API Manual — and her whole thing is Initializes and registers CRQ with hypervisor. That’s the name, that’s the assignment, periodt. 💅

✨ SYNOPSIS ✨

int ibmvscsi_init_crq_queue (struct crq_queue *queue , struct
ibmvscsi_host_data *hostdata , int max_requests );

🎀 ARGUMENTS 🎀

• queue — the crq_queue to initialize and register. She’s getting set up, your honor. 🫶
• hostdata — the ibmvscsi_host_data of host. The host’s data, literally. 💖
• max_requests — maximum requests (unused). Not me pointing out that (unused) is doing zero work but still showing up. 🙈

🦋 DESCRIPTION 🦋

Here’s the tea: it allocates a page for messages, maps it for dma, and registers the crq with the hypervisor. That’s the entire glow-up routine, no extras.

Returns zero on success. Slay. ✨

🌈 SEE ALSO 🌈

Kernel file ./drivers/scsi/ibmvscsi/ibmvscsi.c — plus these absolute icons:

• ibmvscsi_handle_event(9)
• ibmvscsi_release_crq_queue(9)
• crq_queue_next_crq(9)
• ibmvscsi_send_crq(9)
• ibmvscsi_task(9)
• ibmvscsi_reset_crq_queue(9)
• ibmvscsi_reenable_crq_queue(9)
• initialize_event_pool(9)
• release_event_pool(9)
• valid_event_struct(9)
• free_event_struct(9)
• get_event_struct(9)
• init_event_struct(9)
• unmap_cmd_data(9)
• map_sg_data(9)
• map_data_for_srp_cmd(9)
• purge_requests(9)
• ibmvscsi_set_request_limit(9)
• ibmvscsi_reset_host(9)
• ibmvscsi_timeout(9)
• ibmvscsi_send_srp_event(9)
• handle_cmd_rsp(9)
• lun_from_dev(9)
• ibmvscsi_queuecommand_lck(9)
• map_persist_bufs(9)
• unmap_persist_bufs(9)
• login_rsp(9)
• send_srp_login(9)
• capabilities_rsp(9)
• send_mad_capabilities(9)
• fast_fail_rsp(9)
• enable_fast_fail(9)
• adapter_info_rsp(9)
• send_mad_adapter_info(9)
• ibmvscsi_eh_host_reset_handler(9)
• ibmvscsi_handle_crq(9)
• ibmvscsi_sdev_configure(9)
• ibmvscsi_change_queue_depth(9)
• ibmvscsi_get_desired_dma(9)
• ibmvscsi_resume(9)

Mwah 💋 — this one’s from source/version ./drivers/scsi/ibmvscsi, dated October 2026.