rpaphp_add_slot(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… rpaphp_add_slot(9) πŸ’…

okay so bestie, welcome to the Kernel API Manual β€” this is the page for rpaphp_add_slot, and honestly it's giving "small function, big responsibilities." Let's get into it ✨


🌸 NAME 🌸

rpaphp_add_slot β€” declare a hotplug slot to the hotplug subsystem. that's it, that's the vibe πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

int rpaphp_add_slot (struct device_node *dn );

πŸ’– ARGUMENTS πŸ’–

  • dn β€” device node of the slot. literally the thing you're handing over, no cap 🫢

✨ DESCRIPTION ✨

okay so here's the tea: this subroutine registers a hotpluggable slot with the PCI hotplug infrastructure. main character energy fr πŸ’…

when does it get called? two moods:

  1. typically during boot time β€” if the hotplug slots are present at boot time πŸŒ…
  2. later, by the dlpar add code β€” if the slot is being dynamically added during runtime πŸ”₯

and now the plot twist 😭 β€” if the device node points at an embedded (built-in) slot, this routine will just return without doing anything, because embedded slots cannot be hotplugged. like, it's not allowed, it's simply not that kind of slot, periodt πŸ’€

🫢 good-to-know: to remove a slot, it suffices to call rpaphp_deregister_slot. one call, that's all, slay πŸ‘‘

πŸ”₯ SEE ALSO πŸ”₯

go read those next bestie, iykyk 🌈⭐


aaaand that's the whole page! πŸ’œ this iconic little entry lives under ./drivers/pci/hotplug, dated October 2026, and it's brought to you as rpaphp_add_slot(9) β€” mwah, go touch some device nodes πŸ§šπŸ’–

πŸ“¦ where this page comes from