zpci_create_device(9)

🌸 NAME 🌸

zpci_create_device — Create a new zpci_dev and add it to the zbus.

okay so this is the zpci_create_device(9) page from the Kernel API Manual, and it is literally the main character of making a zPCI device appear. Bestie, we are allocating and registering, no cap. 💅✨

✨ SYNOPSIS ✨

struct zpci_dev * zpci_create_device (u32 fid , u32 fh , enum zpci_state state );

💖 ARGUMENTS 💖

• fid — Function ID of the device to be created. It is giving “which device are we even talking about” energy.
• fh — Current Function Handle of the device to be created. The handle of the moment, fr fr.
• state — Initial state after creation — either Standby or Configured. Pick your beginning, bestie.

🦋 DESCRIPTION 🦋

It allocates a new struct zpci_dev and queries the platform for its details. The way that works is very “ask the platform nicely and hope for a slay.” If successful, the device can subsequently be added to the zPCI subsystem using zpci_add_device. That is the sequel, and yes, it is iconic.

🎀 RETURN 🎀

Returns the zdev on success or an error pointer otherwise. So: good vibes = zdev, bad vibes = error pointer. Vibe check complete. 😭💀

👑 SEE ALSO 👑

Kernel file: ./arch/s390/pci/pci.c

• zpci_hot_reset_device(9)
• zpci_add_device(9)
• zpci_scan_configured_device(9)
• zpci_deconfigure_device(9)
• zpci_device_reserved(9)
• zpci_clear_error_state(9)
• zpci_reset_load_store_blocked(9)

source/version: ./arch/s390/pci, date: October 2026, page: zpci_create_device(9). Mwah 💋✨