lpfc_debugfs_nvme_trc(9)

💅 lpfc_debugfs_nvme_trc — like, the manual page, but make it make sense

okay bestie so this is a kernel API manual page for lpfc_debugfs_nvme_trc(9) and honestly? it's short, it's sweet, and it's doing exactly one job. let's get into it 🎀

---

✨ NAME ✨

lpfc_debugfs_nvme_trc — Store NVME/NVMET trace log 🦋

like, literally just storing a trace log. that's the whole vibe.

---

🌸 SYNOPSIS 🌸

void lpfc_debugfs_nvme_trc (struct lpfc_hba *phba , char *fmt , uint16_t
data1 , uint16_t data2 , uint32_t data3 );

it returns void, so don't go looking for a return value, there isn't one, periodt 💀

---

💖 ARGUMENTS 💖

• phba — the phba to associate this trace string with for retrieval. it's giving "who does this log belong to" energy 👑
• fmt — format string to be displayed when dumping the log. yes bestie, it's a format string, it does format string things 🎀
• data1 — 1st data parameter to be applied to fmt.
• data2 — 2nd data parameter to be applied to fmt.
• data3 — 3rd data parameter to be applied to fmt.

three data params, numbered, in order, no notes 🌈

---

🦋 DESCRIPTION 🦋

so this routine is used by the driver code to add a debugfs log entry to the nvme trace buffer associated with phba. that's the whole assignment, and it ate 🔥

and here's the cute part: fmt, data1, data2, and data3 are used like printf when displaying the log. so when you dump it later, it prints out pretty. iykyk 💅

ngl, this one is a single-purpose little icon — driver code calls it, log entry gets added, the buffer holds it for later retrieval. no cap, that's it.

---

⭐ SEE ALSO ⭐

🧚 the actual source file

• Kernel file ./drivers/scsi/lpfc/lpfc_debugfs.c

🍓 the trace-and-data girlies

• lpfc_debugfs_disc_trc_data(9), lpfc_debugfs_slow_ring_trc_data(9), lpfc_debugfs_hbqinfo_data(9), lpfc_debugfs_commonxripools_data(9), lpfc_debugfs_multixripools_data(9), lpfc_debugfs_lockstat_data(9)
• lpfc_debugfs_dumpHBASlim_data(9), lpfc_debugfs_dumpHostSlim_data(9), lpfc_debugfs_nodelist_data(9), lpfc_debugfs_nvmestat_data(9), lpfc_debugfs_scsistat_data(9), lpfc_debugfs_ioktime_data(9)
• lpfc_debugfs_nvmeio_trc_data(9), lpfc_debugfs_hdwqstat_data(9)

💜 the trace-and-open girlies

• lpfc_debugfs_disc_trc(9), lpfc_debugfs_slow_ring_trc(9), lpfc_debugfs_disc_trc_open(9), lpfc_debugfs_slow_ring_trc_open(9), lpfc_debugfs_hbqinfo_open(9), lpfc_debugfs_multixripools_open(9)
• lpfc_debugfs_lockstat_open(9), lpfc_debugfs_ras_log_open(9), lpfc_debugfs_dumpHBASlim_open(9), lpfc_debugfs_dumpHostSlim_open(9), lpfc_debugfs_nodelist_open(9)
• lpfc_debugfs_lseek(9), lpfc_debugfs_read(9), lpfc_debugfs_release(9), lpfc_debugfs_multixripools_write(9)

🌈 the idiag extended universe (yes there are SO many, stay with me)

• lpfc_idiag_cmd_get(9), lpfc_idiag_open(9), lpfc_idiag_release(9), lpfc_idiag_cmd_release(9), lpfc_idiag_pcicfg_read(9), lpfc_idiag_pcicfg_write(9)
• lpfc_idiag_baracc_read(9), lpfc_idiag_baracc_write(9), lpfc_idiag_queinfo_read(9), lpfc_idiag_que_param_check(9), lpfc_idiag_queacc_read_qe(9), lpfc_idiag_queacc_read(9), lpfc_idiag_queacc_write(9)
• lpfc_idiag_drbacc_read_reg(9), lpfc_idiag_drbacc_read(9), lpfc_idiag_drbacc_write(9), lpfc_idiag_ctlacc_read_reg(9), lpfc_idiag_ctlacc_read(9), lpfc_idiag_ctlacc_write(9)
• lpfc_idiag_mbxacc_get_setup(9), lpfc_idiag_mbxacc_read(9), lpfc_idiag_mbxacc_write(9)
• lpfc_idiag_extacc_avail_get(9), lpfc_idiag_extacc_alloc_get(9), lpfc_idiag_extacc_drivr_get(9), lpfc_idiag_extacc_write(9), lpfc_idiag_extacc_read(9)

👑 the setup-and-teardown main characters

• lpfc_debugfs_initialize(9), lpfc_debugfs_terminate(9), lpfc_debug_dump_all_queues(9)

---

and that's the whole page, bestie 💖 it lives in ./drivers/scsi/lpfc, it's stamped October 2026, and it answers to the name lpfc_debugfs_nvme_trc(9). go forth and trace your nvme, you're gonna slay ✨🫶