pci_load_saved_state(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ pci_load_saved_state(9) πŸŽ€

okay so bestie, welcome to the Kernel API Manual, section 9 β€” this is the pci_load_saved_state page and it's genuinely such a little main-character function. The whole vibe: you saved a PCI device's state earlier, and now you wanna shove it back in. Iconic. Let's get into it πŸ’…


✨ NAME ✨

pci_load_saved_state β€” reload the provided save state into struct pci_dev.

no cap, that's literally the whole thing. you hand it a blob of saved state and it goes right back into the device struct 🫢


🌸 SYNOPSIS 🌸

int pci_load_saved_state (struct pci_dev *dev , struct pci_saved_state *state );

she returns an int, bestie. take that however you like 😌


πŸ¦‹ ARGUMENTS πŸ¦‹

  • dev β€” the PCI device we're dealing with. the one we're doing all this for. the star of the show πŸ‘‘
  • state β€” the saved state, and the manual is very specific here: it's the saved state returned from pci_store_saved_state. so like, don't just vibe-check any random pointer in there, use the one you got from the store function, iykyk πŸ“

πŸ’œ SEE ALSO πŸ’œ

first up, the kernel file this lives in β€” keep it noted:

./drivers/pci/pci.c

and now the extended family, because this page has a lot of siblings and we are naming every single one, no skipping, we don't do that here πŸ’€

like I said. huge family. every one of them made the list and every one of them stays on the list πŸ’–


and that's the page!! 🫢✨

cute little sign-off for the source and the date, because she deserves it: this one lives in ./drivers/pci and it's dated October 2026. go reload that state bestie, you got this πŸŽ€πŸ’…

πŸ“¦ where this page comes from