qla4xxx_pci_mmio_enabled(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… qla4xxx_pci_mmio_enabled(9) β€” the whole kernel API manual, but make it make sense

okay so bestie, we're in the qla4xxx_pci_mmio_enabled(9) page today β€” that's the title and the manual name all at once, iconic of it β€” and honestly? This one's a tiny little function with a very specific job. Let me put you on. 🫢


✨ NAME ✨

qla4xxx_pci_mmio_enabled β€” gets called if qla4xxx_pci_error_detected() returns PCI_ERS_RESULT_CAN_RECOVER and read/write to the device still works.

that's it. that's the whole vibe check. it's the "okay so the PCI error recovery thing said we can recover, and the device is still answering reads and writes, so like… we in business" callback. no cap. πŸ’–


πŸŽ€ SYNOPSIS πŸŽ€

pci_ers_result_t qla4xxx_pci_mmio_enabled (struct pci_dev *pdev );

like, it takes one thing and returns a pci_ers_result_t, periodt. πŸ’…


🌸 ARGUMENTS 🌸

  • pdev β€” PCI device pointer. literally the PCI device. that's the whole thing. the device in question. the one whose MMIO we're checking on. she's pointing at the device, bestie. πŸ¦‹

πŸ‘‘ SEE ALSO πŸ‘‘

the kernel file in question is ./drivers/scsi/qla4xxx/ql4_os.c, and like… it's a whole extended universe of friends in there. all of these, not one skipped, i would never do you like that:

that's forty-eight little hyperlinks-to-nowhere, all accounted for, none of them ghosted. πŸ˜­πŸ’œ


real talk though: this page is thin on purpose. the whole contract is in that NAME line β€” the call only happens when qla4xxx_pci_error_detected() hands back PCI_ERS_RESULT_CAN_RECOVER and reads and writes to the device are still working. that's the condition. don't invent more. 🧚

okay and lastly, the boring-but-mandatory sign-off bestie: this one lives under ./drivers/scsi/qla4xxx, it's dated October 2026, and the page is qla4xxx_pci_mmio_enabled(9) β€” same name as the top, because symmetry ate and left no crumbs. πŸŒˆβ­πŸ’–

πŸ“¦ where this page comes from