mpi3mr_set_t..._data_in_hdb(9)
π
mpi3mr_set_trigger_data_in_hdb β a Kernel API Manual moment
okay so bestie, we're in the Kernel API Manual and today's main character is mpi3mr_set_trigger_data_in_hdb(9). yes that's a whole function name, no we're not scared of it π
β¨ NAME β¨
mpi3mr_set_trigger_data_in_hdb β literally updates the HDB trigger type and the trigger data. that's it, that's the whole vibe π
πΈ SYNOPSIS πΈ
void mpi3mr_set_trigger_data_in_hdb (struct diag_buffer_desc *hdb , u8
type , union mpi3mr_trigger_data *trigger_data , bool force );
like, void return, four things going in. she takes what she takes and gives nothing back (respect) π
π¦ ARGUMENTS π¦
hdbβ the HDB pointer. that's the diag buffer descriptor bestie, keep up π«Άtypeβ the trigger type. which flavour of trigger are we doing today πtrigger_dataβ pointer to the trigger data information. all the juicy details live here β¨forceβ the trigger overwrite flag. are we forcing the overwrite or are we being polite about it π
π DESCRIPTION π
so what does she actually do? she updates the trigger type and the trigger data, based on whatever parameters you pass into her. that's the whole assignment and she ate π₯
ngl it's giving "small function, big responsibility" energy. the parameters are literally the whole plot π
β RETURN β
Nothing. not 0, not an error code, not even a little guy. nothing. she returns void and she's thriving π§
π SEE ALSO π
first up, the kernel file where this all lives:
./drivers/scsi/mpi3mr/mpi3mr_app.c
and now the full friend group, no cap, every single one of them:
mpi3mr_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_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_app_save_logdata_th(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)
and that's the page bestie!! π this lil masterpiece comes to you from the source ./drivers/scsi/mpi3mr, dated October 2026, and it's filed under mpi3mr_set_t..._data_in_hdb(9) β go read the rest of them, iykyk π
π¦ 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