mpt_raid_phys_disk_pg1(9)

🎀 mpt_raid_phys_disk_pg1(9) 🎀

okay so bestie, welcome to the mpt_raid_phys_disk_pg1(9) page — it's from the Kernel API Manual and it is literally your cheat sheet for pulling the phys disk page 1 payload. no cap, it's a whole vibe. let's go 💅

---

✨ NAME ✨

mpt_raid_phys_disk_pg1 — it returns phys disk page 1. that's it, that's the whole name. iconic behavior tbh 🫶

---

🌸 SYNOPSIS 🌸

int mpt_raid_phys_disk_pg1 (MPT_ADAPTER *ioc , u8 phys_disk_num ,
       RaidPhysDiskPage1_t *phys_disk );

look at her. three args, one int return, main character energy fr fr ✨

---

🦋 ARGUMENTS 🦋

• ioc — pointer to a Adapter Structure. she's the adapter, she holds the lore 🧚
• phys_disk_num — the io unit unique phys disk num, generated by the ioc. so the ioc made it, the ioc knows it, and you're just here for the ride 😭
• phys_disk — the requested payload data, returned to you. this is where the good stuff lands 💖

---

👑 RETURN 👑

• 0 — success bestie!! we ate 🍓
• -EFAULT — the read of config page header failed, or the data pointer was not NULL. that's the vibe check failing, sorry 🙈
• -ENOMEM — pci_alloc failed. no memory, no slay.💀

---

💜 SEE ALSO 💜

fair warning, this list is long. like, genuinely long. but every one of these is a real sibling and we do not skip anyone here, periodt. 💅

Kernel file ./drivers/message/fusion/mptbase.c, plus:

mpt_get_cb_idx(9), mpt_is_discovery_complete(9), mpt_remove_dead_ioc_func(9), mpt_fault_reset_work(9), mpt_interrupt(9), mptbase_reply(9), mpt_register(9), mpt_deregister(9), mpt_event_register(9), mpt_event_deregister(9), mpt_reset_register(9), mpt_reset_deregister(9), mpt_device_driver_register(9), mpt_device_driver_deregister(9), mpt_get_msg_frame(9), mpt_put_msg_frame(9), mpt_put_msg_frame_hi_pri(9), mpt_free_msg_frame(9), mpt_add_sge(9), mpt_add_sge_64bit(9), mpt_add_sge_64bit_1078(9), mpt_add_chain(9), mpt_add_chain_64bit(9), mpt_send_handshake_request(9), mpt_host_page_access_control(9), mpt_host_page_alloc(9), mpt_verify_adapter(9), mpt_get_product_name(9), mpt_mapresources(9), mpt_attach(9), mpt_detach(9), mpt_suspend(9), mpt_resume(9), mpt_do_ioc_recovery(9), mpt_detect_bound_ports(9), mpt_adapter_disable(9), mpt_adapter_dispose(9), MptDisplayIocCapabilities(9), MakeIocReady(9), mpt_GetIocState(9), GetIocFacts(9), GetPortFacts(9), SendIocInit(9), SendPortEnable(9), mpt_alloc_fw_memory(9), mpt_free_fw_memory(9), mpt_do_upload(9), mpt_downloadboot(9), KickStart(9), mpt_diag_reset(9), SendIocReset(9), initChainBuffers(9), PrimeIocFifos(9), mpt_handshake_req_reply_wait(9), WaitForDoorbellAck(9), WaitForDoorbellInt(9), WaitForDoorbellReply(9), GetLanConfigPages(9), mptbase_sas_persist_operation(9), GetIoUnitPage2(9), mpt_GetScsiPortSettings(9), mpt_readScsiDevicePageHeaders(9), mpt_inactive_raid_list_free(9), mpt_inactive_raid_volumes(9), mpt_raid_phys_disk_pg0(9), mpt_raid_phys_disk_get_num_paths(9), mpt_findImVolumes(9), SendEventNotification(9), SendEventAck(9), mpt_config(9), mpt_ioc_reset(9), procmpt_create(9), procmpt_destroy(9), mpt_print_ioc_summary(9), mpt_set_taskmgmt_in_progress_flag(9), mpt_clear_taskmgmt_in_progress_flag(9), mpt_halt_firmware(9), mpt_SoftResetHandler(9), mpt_Soft_Hard_ResetHandler(9), mpt_HardResetHandler(9), ProcessEventNotification(9), mpt_fc_log_info(9), mpt_spi_log_info(9), mpt_sas_log_info(9), mpt_iocstatus_info_config(9), mpt_iocstatus_info(9), fusion_init(9), fusion_exit(9)

like I said. the whole extended fam showed up to the group chat 🌈😭

---

and that's the page bestie!! short, sweet, three return values, and one absolutely massive SEE ALSO section. drink some water, go read mpt_raid_phys_disk_pg0(9) next, and remember: it lives in ./drivers/message/fusion, dated October 2026, and it is, forever, mpt_raid_phys_disk_pg1(9). mwah 💋🎀✨