zpci_report_status(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🩷 zpci_report_status(9) β€” the Kernel API Manual glow-up 🩷

okay so bestie, welcome to the zpci_report_status(9) page β€” straight out of the Kernel API Manual, and tbh it's a little baddie that does one thing and does it well. let's get into it πŸ’…


✨ NAME ✨

zpci_report_status β€” Report the status of operations on a PCI device πŸŽ€

like… that's the whole vibe. it reports status. on a PCI device. iconic behavior honestly.


πŸ¦‹ SYNOPSIS πŸ¦‹

int zpci_report_status (struct zpci_dev *zdev , struct pci_dev *pdev ,
       const char *operation , const char *status );

copy it exactly, no cap β€” that's the signature, character for character, and we stan a consistent prototype. πŸ”₯


🌸 ARGUMENTS 🌸

  • zdev β€” the zPCI device you're reporting status for, like, the main character of this whole situation πŸ‘‘
  • pdev β€” the PCI device that's associated with the zdev if there is one β€” and if there isn't? NULL. no device, no problem πŸ’€
  • operation β€” a string representing the operation being reported, i.e. what went down
  • status β€” a string representing the status of that operation, i.e. how it went 🫢

πŸ’– DESCRIPTION πŸ’–

so what does this function actually do, you ask? okay so:

it creates a human readable report about an operation β€” think stuff like PCI device recovery β€” and then it forwards that report to the platform using the SCLP Write Event Data mechanism. slay. ✨

and it's not just the operation and status strings, bestie. the report also scoops up extra info about the device that's deemed useful for debug, like:

  • the currently bound device driver, if any
  • the error state

plus β€” and this is lowkey the cute part β€” a string representation of pci_debug_msg_id gets included too, or as much as fits. not me fitting the whole debug id in… or not. whatever fits, fits. πŸ™ˆ


⭐ RETURN ⭐

  • 0 on success πŸŽ‰
  • an error code < 0 otherwise 😭

that's it. zero means we ate, negative means something's giving error energy.


🌈 SEE ALSO 🌈

  • Kernel file ./arch/s390/pci/pci_report.c β€” go read the source, iykyk 🧚
fr fr, if you're debugging zPCI stuff on s390, that file is your bestie too.

and that's the page!! mwah πŸ’‹

this lil gem lives in ./arch/s390/pci, dated October 2026 β€” so like, future vibes only. byeee bestie, go report some statuses responsibly πŸ“πŸ’œ

πŸ“¦ where this page comes from