qed_recovery_prolog(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… qed_recovery_prolog(9) β€” bestie's field guide

okay so this page lives in the Kernel API Manual, section 9 (the kernel-API girlies, you know the ones ✨). Pull up a chair, we're talking about the very first thing your recovery handler has to do. no cap. 🫢


🌸 NAME 🌸

qed_recovery_prolog β€” a recovery handler must call this function as its first step. like, step one, before anything else, no negotiating πŸ’…. and bestie, it's assumed that the handler is not run from an interrupt context. so don't come at it from interrupt land, that's not the vibe it was built for 🚫⚑


πŸŽ€ SYNOPSIS πŸŽ€

int qed_recovery_prolog (struct qed_dev *cdev );

that's it. that's the whole call. iconic minimalism πŸ‘‘


πŸ¦‹ ARGUMENTS πŸ¦‹

  • cdev β€” the Qed dev pointer. yes, that one. hand it over and let it cook πŸ“

⭐ RETURN ⭐

int. that's literally the whole documented return type β€” int, periodt. no extra lore, no secret second value, nothing hidden. just an int doing its little int thing 😌


πŸ’œ SEE ALSO πŸ’œ

the source of truth herself lives in the kernel file:

./drivers/net/ethernet/qlogic/qed/qed_mcp.h

and omg the friend group is huge. like genuinely enormous. iykyk. every single one of these is linked below, in the exact order they were handed to me, no skipping, no merging, no "eh that one's boring" β€” we respect all of them equally 🫑

the link-params-and-state girlies:

the command-and-drain crew:

the recovery/main-character section (yes this is us πŸ”₯):

the override update girlies:

the NVM girls (they never sleep 😭):

the BIST squad:

the TLV + debug + speed-check trio:

init / free / events / load-unload β€” the lifecycle besties 🌈:

resources + flr + eswitch energy 🧚:

capabilities & smart AN (she's smart, she's an, she's supported):

nvm info populate/free, because balance ✨:

engine config + ppfid bitmap β€” the deep lore πŸŒ€:

nvm cfg getters and setters, a matched set slay πŸ’…:

and finally the ESL girlies, closing us out 🌸:


real talk bestie: the one rule that actually matters here is call it first. recovery handler, first step, qed_recovery_prolog. and it is assumed you're not in an interrupt context. that's the whole assignment πŸŽ€

and that's the page!! source/version vibes: ./drivers/net/ethernet/qlogic/qed, dated October 2026, filed under qed_recovery_prolog(9) in the Kernel API Manual (section 9). go call it first, bestie, you're gonna ate πŸ’–βœ¨πŸ‘‘

πŸ“¦ where this page comes from