_ctl_eventquery(9)

✨ _ctl_eventquery — the manual page for the MPT3EVENTQUERY main handler ✨

Okay bestie, so this is from the Kernel API Manual and it's literally all about _ctl_eventquery(9) — the main handler for the MPT3EVENTQUERY opcode. It's giving kernel-level main character energy, no cap. 🎀

---

🌸 NAME 🌸

_ctl_eventquery — main handler for MPT3EVENTQUERY opcode

---

🦋 SYNOPSIS 🦋

long _ctl_eventquery (struct MPT3SAS_ADAPTER *ioc , void __user *arg );

---

💖 ARGUMENTS 💖

• ioc — the per adapter object, like the whole vibe of this specific adapter instance 💅
• arg — user space buffer containing ioctl content, aka the stuff your userspace sent over 🫶

---

🔥 SEE ALSO 🔥

Okay so this is a long list, but we're not skipping a single one because every reference matters, fr fr. All of these are literally siblings in the same kernel family:

Kernel file ./drivers/scsi/mpt3sas/mpt3sas_ctl.c — and then we've got enum block_state(9), _ctl_display_some_debug(9), mpt3sas_ctl_done(9), _ctl_check_event_type(9), mpt3sas_ctl_add_to_event_log(9), mpt3sas_ctl_event_callback(9), _ctl_verify_adapter(9), mpt3sas_ctl_pre_reset_handler(9), mpt3sas_ctl_clear_outstanding_ioctls(9), mpt3sas_ctl_reset_done_handler(9), _ctl_fasync(9), _ctl_poll(9), _ctl_set_task_mid(9), _ctl_send_mctp_passthru_req(9), _ctl_do_mpt_command(9), _ctl_getiocinfo(9), _ctl_eventenable(9), _ctl_eventreport(9), _ctl_do_reset(9), _ctl_btdh_search_sas_device(9), _ctl_btdh_search_pcie_device(9), _ctl_btdh_search_raid_device(9), _ctl_btdh_mapping(9), _ctl_diag_capability(9), _ctl_diag_get_bufftype(9), _ctl_diag_register_2(9), mpt3sas_enable_diag_buffer(9), _ctl_diag_register(9), _ctl_diag_unregister(9), _ctl_diag_query(9), mpt3sas_send_diag_release(9), _ctl_diag_release(9), _ctl_diag_read_buffer(9), _ctl_addnl_diag_query(9), _ctl_enable_diag_sbr_reload(9), _ctl_compat_mpt_command(9), _ctl_ioctl_main(9), _ctl_get_mpt_mctp_passthru_adapter(9), mpt3sas_get_device_count(9), _ctl_ioctl(9), _ctl_mpt2_ioctl(9), _ctl_ioctl_compat(9), _ctl_mpt2_ioctl_compat(9), version_fw_show(9), version_bios_show(9), version_mpi_show(9), version_product_show(9), version_nvdata_persistent_show(9), version_nvdata_default_show(9), board_name_show(9), board_assembly_show(9), board_tracer_show(9), io_delay_show(9), device_delay_show(9), fw_queue_depth_show(9), host_sas_address_show(9), logging_level_show(9), fwfault_debug_show(9), ioc_reset_count_show(9), reply_queue_count_show(9), BRM_status_show(9), host_trace_buffer_size_show(9), host_trace_buffer_show(9), host_trace_buffer_enable_show(9), diag_trigger_master_show(9), diag_trigger_master_store(9), diag_trigger_event_show(9), diag_trigger_event_store(9), diag_trigger_scsi_show(9), diag_trigger_scsi_store(9), diag_trigger_mpi_show(9), diag_trigger_mpi_store(9), drv_support_bitmap_show(9), enable_sdev_max_qd_show(9), enable_sdev_max_qd_store(9), sas_address_show(9), sas_device_handle_show(9), sas_ncq_prio_supported_show(9), sas_ncq_prio_enable_show(9), mpt3sas_ctl_init(9), mpt3sas_ctl_release(9), and mpt3sas_ctl_exit(9).

Like, that's the whole squad and they all ate. 💀👑

---

Bestie, this is kernel API stuff, so no cap — handle it with care. It's not dangerous in the manual page, but it's real kernel code, so respect the vibes.

---

And that's the whole page, bestie! Sending you love from the ./drivers/scsi/mpt3sas source and the October 2026 version — mwah! 💖✨🎀