qed_dbg_mcp...ump_buf_size(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– qed_dbg_mcp_trace_get_dump_buf_size(9) πŸ’–

okay so bestie, this is a Kernel API Manual page, and the header was out here looking like qed_dbg_mcp...ump_buf_size(9) because manpage headers really said β€œabbreviate her.” The full function name is right up there, and it’s giving β€œtell me the buffer size for mcp trace results” energy. No cap. πŸ¦‹

✨ NAME ✨

qed_dbg_mcp_trace_get_dump_buf_size β€” Returns the required buffer size for mcp trace results. That’s the whole vibe: it tells you how big the buffer needs to be. πŸŽ€

🌸 SYNOPSIS 🌸

enum dbg_status qed_dbg_mcp_trace_get_dump_buf_size (struct qed_hwfn
       *p_hwfn , struct qed_ptt *p_ptt , u32 *buf_size );

πŸŽ€ ARGUMENTS πŸŽ€

  • p_hwfn β€” HW device data. Like, the hardware device data, bestie.
  • p_ptt β€” Ptt window used for writing the registers.
  • buf_size β€” (OUT) Required buffer size (in dwords) for mcp trace data. Yes, in dwords β€” read the label, she’s specific. πŸ’…

πŸ’… RETURN πŸ’…

It returns an error if one of the following holds:

  • The version wasn’t set.
  • The trace data in MCP scratchpad contain an invalid signature.
  • The bundle ID in NVRAM is invalid.
  • The trace meta data cannot be found (in NVRAM or image file).

Otherwise, returns ok. Periodt. ✨

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file: ./drivers/net/ethernet/qlogic/qed/qed_dbg_hsi.h

And now the whole bestie tag list, iykyk:


mwah πŸ’‹ that’s the page! It’s from ./drivers/net/ethernet/qlogic/qed, dated October 2026, and the footer was still out here saying qed_dbg_mcp...ump_buf_size(9). byeee πŸŽ€

πŸ“¦ where this page comes from