mpi3mr_app_save_logdata_th(9)
πΎ mpi3mr_app_save_logdata_th(9) β bestie edition πΎ
okay so this is a page from the Kernel API Manual, and it's all about one lil function living in the mpi3mr driver family. buckle up π
β¨ NAME β¨
mpi3mr_app_save_logdata_th β literally the "Save Log Data events" girlie π
π¦ SYNOPSIS π¦
void mpi3mr_app_save_logdata_th (struct mpi3mr_ioc *mrioc , char
*event_data , u16 event_data_size );
no cap, that's the whole signature. returns void, so she gives you nothing back β she's giving mystery, she's giving nothing. π
πΈ ARGUMENTS πΈ
mriocβ your adapter instance reference, aka the VIP pass π«Άevent_dataβ the event data that's chillin' alongside the log data eventevent_data_sizeβ how much of that event data you're copying, inu16flavour
π DESCRIPTION π
so here's the tea β β if log data event caching has been enabled by the applications, this function goes ahead and saves the log data into the circular queue π‘ and then sends an async signal SIGIO to say hey bestie, the firmware pushed an async event, and the event monitoring applications need to know π£
that's it. that's the whole vibe. it's an announcement girlie β she saves, then she signals.
β RETURN β
Nothing. zip. nada. void through and through π«₯
ngl, "nothing" is her whole personality and honestly? iconic.
π₯ SEE ALSO π₯
buckle in bestie, this list is long β she knows everybody at the party π
Kernel file ./drivers/scsi/mpi3mr/mpi3mr_app.cmpi3mr_alloc_trace_buffer(9)mpi3mr_alloc_diag_bufs(9)mpi3mr_issue_diag_buf_post(9)mpi3mr_post_diag_bufs(9)mpi3mr_issue_diag_buf_release(9)mpi3mr_process_trigger(9)mpi3mr_global_trigger(9)mpi3mr_scsisense_trigger(9)mpi3mr_event_trigger(9)mpi3mr_reply_trigger(9)mpi3mr_get_num_trigger(9)mpi3mr_refresh_trigger(9)mpi3mr_release_diag_bufs(9)mpi3mr_set_trigger_data_in_hdb(9)mpi3mr_set_trigger_data_in_all_hdb(9)mpi3mr_hdbstatuschg_evt_th(9)mpi3mr_diag_buffer_for_type(9)mpi3mr_bsg_pel_abort(9)mpi3mr_bsg_verify_adapter(9)mpi3mr_bsg_refresh_hdb_triggers(9)mpi3mr_bsg_upload_hdb(9)mpi3mr_bsg_repost_hdb(9)mpi3mr_bsg_query_hdb(9)mpi3mr_enable_logdata(9)mpi3mr_get_logdata(9)mpi3mr_bsg_pel_enable(9)mpi3mr_get_all_tgt_info(9)mpi3mr_get_change_count(9)mpi3mr_bsg_adp_reset(9)mpi3mr_bsg_populate_adpinfo(9)mpi3mr_bsg_process_drv_cmds(9)mpi3mr_total_num_ioctl_sges(9)mpi3mr_bsg_build_sgl(9)mpi3mr_get_nvme_data_fmt(9)mpi3mr_build_nvme_sgl(9)mpi3mr_build_nvme_prp(9)mpi3mr_map_data_buffer_dma(9)mpi3mr_bsg_process_mpt_cmds(9)mpi3mr_bsg_request(9)mpi3mr_bsg_exit(9)mpi3mr_bsg_node_release(9)mpi3mr_bsg_init(9)version_fw_show(9)fw_queue_depth_show(9)op_req_q_count_show(9)reply_queue_count_show(9)reply_qfull_count_show(9)logging_level_show(9)logging_level_store(9)adp_state_show(9)fwfault_count_show(9)sas_address_show(9)device_handle_show(9)persistent_id_show(9)sas_ncq_prio_supported_show(9)sas_ncq_prio_enable_show(9)
mwah π this page lives in ./drivers/scsi/mpi3mr, it's dated October 2026, and it's serving Kernel API Manual realness. slay, bye β¨π
π¦ 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