logging_level_store(9)
π logging_level_store(9) π
okay so real talk, this one lives in the Kernel API Manual and it's basically the little sysfs switch that cranks the debug dial for one specific controller π
β¨ NAME β¨
logging_level_store β change controller debug level. yes bestie, that's the whole vibe. you're literally adjusting how chatty the driver gets about a single controller π¦
πΈ SYNOPSIS πΈ
ssize_t logging_level_store (struct device *dev , struct
device_attribute *attr , const char *buf , size_t count );
π ARGUMENTS π
devβ the class device, aka the thing you're poking at πattrβ device attributes, standard sysfs machinery, nothing spicy πbufβ buffer to copy, this is where your value lives πcountβ size of the buffer, gotta know how much to scoop up π
π§ DESCRIPTION π§
so it's a sysfs 'read/write' shost attribute, and what it does is change the current debug log level that the driver uses for the specific controller. one controller, one level. it's giving main character energy for exactly one host π no cap.
β RETURN β
strlen return π« (that's it, that's the whole return story)
π₯ SEE ALSO π₯
the lore runs deep, here's the whole friend group π«Ά
- Kernel file
./drivers/scsi/mpi3mr/mpi3mr_app.c 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_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_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)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)
okay that's the page!! it comes from ./drivers/scsi/mpi3mr, dated October 2026 β mwah, iconic, no notes π
β¨π
π¦ 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