mpi3mr_cfg_get_sas_phy_pg1(9)
π mpi3mr_cfg_get_sas_phy_pg1(9) β Kernel API Manual β¨
okay so bestie, welcome to the Kernel API Manual entry for mpi3mr_cfg_get_sas_phy_pg1(9) β yes that's a real function name and yes we're gonna read it together π«Ά
πΈ NAME πΈ
mpi3mr_cfg_get_sas_phy_pg1 β read the current SAS Phy page1, no cap π
π SYNOPSIS π
int mpi3mr_cfg_get_sas_phy_pg1 (struct mpi3mr_ioc *mrioc , u16
*ioc_status , struct mpi3_sas_phy_page1 *phy_pg1 , u16 pg_sz , u32 form
, u32 form_spec );
like, that's the whole signature, copy it exactly, iykyk β¨
π¦ ARGUMENTS π¦
mriocβ your adapter instance reference, the main character of this whole function nglioc_statusβ a pointer where we return the ioc status π«Άphy_pg1β pointer to return the SAS Phy page 1 into, that's the whole vibepg_szβ the size of the memory you allocated to the page pointer, pls don't lie about this one πformβ the form used for addressing the pageform_specβ form-specific info, like the phy number, the little details that matter π
π DESCRIPTION π
So this is the handler for a config page read β specifically for one specific SAS Phy page1. Iconic, honestly.
The ioc_status ends up holding the controller's returned ioc_status. And here's the important part, bestie, listen up: this routine does not check ioc_status to decide whether the page read succeeded or not. That's literally the caller's job. It's giving "I did my part, you do yours" energy π
π¨ fr fr, do not assume success just because the function came back β check that ioc_status yourself, it's on you π
β RETURN β
0 on success, non-zero on failure. That's it, that's the whole vibe check π
π₯ SEE ALSO π₯
All the sibling functions living in the kernel file ./drivers/scsi/mpi3mr/mpi3mr_fw.c β go say hi to the whole fam π
mpi3mr_get_reply_desc(9)mpi3mr_process_op_reply_q(9)mpi3mr_blk_mq_poll(9)mpi3mr_isr_poll(9)mpi3mr_request_irq(9)mpi3mr_setup_isr(9)mpi3mr_reset_rc_name(9)mpi3mr_reset_type_name(9)mpi3mr_is_fault_recoverable(9)mpi3mr_print_fault_info(9)mpi3mr_save_fault_info(9)mpi3mr_get_iocstate(9)mpi3mr_free_ioctl_dma_memory(9)mpi3mr_alloc_ioctl_dma_memory(9)mpi3mr_fault_uevent_emit(9)mpi3mr_clear_reset_history(9)mpi3mr_issue_and_process_mur(9)mpi3mr_revalidate_factsdata(9)mpi3mr_bring_ioc_ready(9)mpi3mr_soft_reset_success(9)mpi3mr_diagfault_success(9)mpi3mr_set_diagsave(9)mpi3mr_issue_reset(9)mpi3mr_admin_request_post(9)mpi3mr_free_op_req_q_segments(9)mpi3mr_free_op_reply_q_segments(9)mpi3mr_delete_op_reply_q(9)mpi3mr_alloc_op_reply_q_segments(9)mpi3mr_alloc_op_req_q_segments(9)mpi3mr_create_op_reply_q(9)mpi3mr_create_op_req_q(9)mpi3mr_create_op_queues(9)mpi3mr_op_request_post(9)mpi3mr_check_rh_fault_ioc(9)mpi3mr_sync_timestamp(9)mpi3mr_print_pkg_ver(9)mpi3mr_watchdog_work(9)mpi3mr_start_watchdog(9)mpi3mr_stop_watchdog(9)mpi3mr_setup_admin_qpair(9)mpi3mr_issue_iocfacts(9)mpi3mr_check_reset_dma_mask(9)mpi3mr_process_factsdata(9)mpi3mr_alloc_reply_sense_bufs(9)mpimr_initialize_reply_sbuf_queues(9)mpi3mr_issue_iocinit(9)mpi3mr_unmask_events(9)mpi3mr_issue_event_notification(9)mpi3mr_process_event_ack(9)mpi3mr_alloc_chain_bufs(9)mpi3mr_port_enable_complete(9)mpi3mr_issue_port_enable(9)mpi3mr_repost_diag_bufs(9)mpi3mr_read_tsu_interval(9)mpi3mr_print_ioc_info(9)mpi3mr_cleanup_resources(9)mpi3mr_setup_resources(9)mpi3mr_enable_events(9)mpi3mr_init_ioc(9)mpi3mr_reinit_ioc(9)mpi3mr_memset_op_reply_q_buffers(9)mpi3mr_memset_op_req_q_buffers(9)mpi3mr_memset_buffers(9)mpi3mr_free_mem(9)mpi3mr_issue_ioc_shutdown(9)mpi3mr_cleanup_ioc(9)mpi3mr_drv_cmd_comp_reset(9)mpi3mr_flush_drv_cmds(9)mpi3mr_pel_wait_post(9)mpi3mr_pel_get_seqnum_post(9)mpi3mr_pel_wait_complete(9)mpi3mr_pel_get_seqnum_complete(9)mpi3mr_check_op_admin_proc(9)mpi3mr_soft_reset_handler(9)mpi3mr_post_cfg_req(9)mpi3mr_process_cfg_req(9)mpi3mr_cfg_get_dev_pg0(9)mpi3mr_cfg_get_sas_phy_pg0(9)mpi3mr_cfg_get_sas_exp_pg0(9)mpi3mr_cfg_get_sas_exp_pg1(9)mpi3mr_cfg_get_enclosure_pg0(9)mpi3mr_cfg_get_sas_io_unit_pg0(9)mpi3mr_cfg_get_sas_io_unit_pg1(9)mpi3mr_cfg_set_sas_io_unit_pg1(9)mpi3mr_cfg_get_driver_pg1(9)mpi3mr_cfg_get_driver_pg2(9)
(yes mpimr_initialize_reply_sbuf_queues(9) really is spelled like that, not me, don't come for me π)
π« sign-off bestie π«
This lil page lives in ./drivers/scsi/mpi3mr, dated October 2026, and it's the mpi3mr_cfg_get_sas_phy_pg1(9) manual page in the Kernel API Manual. Go read your ioc_status, hydrate, and stan responsibly π
β¨π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms