mpi3mr_cfg_get_driver_pg2(9)
π« mpi3mr_cfg_get_driver_pg2 β like, the kernel API manual, but make it make sense
okay so bestie, welcome to the mpi3mr_cfg_get_driver_pg2(9) page π
this is a kernel API manual page, and it's literally about reading the current driver page2. That's it. That's the whole vibe. Let's go π«Ά
β¨ SYNOPSIS β¨
int mpi3mr_cfg_get_driver_pg2 (struct mpi3mr_ioc *mrioc , struct
mpi3_driver_page2 *driver_pg2 , u16 pg_sz , u8 page_action );
like, four things go in, one int comes out. simple. iconic. no notes πΈ
π ARGUMENTS π
mriocβ the adapter instance reference. like, which adapter are we talking to, bestie? this one πdriver_pg2β pointer to return driver page 2. yes, it's a pointer tostruct mpi3_driver_page2, and yes it's where the page lands when we're done π¦pg_szβ size of the memory allocated to the page pointer. theu16that tells everyone how much room we've got to work with β¨page_actionβ page action. that's theu8. it's the action. for the page. iykyk π
π DESCRIPTION π
so this routine is the handler for config page read for the driver page2 β the dedicated config-page-read girlie for page2, if you will π
what does it actually do though? it checks ioc_status to decide whether the page read is success or not. literally that's the whole plot. the status says yay β success, the status says nay β not success. main character energy fr fr π₯
β RETURN β
0on success π- non-zero on failure π
that's the entire contract. zero is the good one. anything else, something went sideways π
π¦ SEE ALSO π¦
first up, the kernel file you'll wanna peek at: ./drivers/scsi/mpi3mr/mpi3mr_fw.c β that's where the lore lives π
and now, the extended universe (yes, all of them, in order, no cap):
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_phy_pg1(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)
no bestie i did not skip any of them, i counted, that's all of them, i would never do you like that π
and that's the page! π cute little sign-off time: this manual page comes from the source/version tree at ./drivers/scsi/mpi3mr and it's dated October 2026 β so yeah, it's a lil time traveler. go read your config pages, bestie, you're gonna slay π§ββοΈπβ¨
π¦ 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