vio_cmo_alloc(9)

✨ vio_cmo_alloc(9) ✨

okay bestie 🫶 welcome to the Kernel API Manual page for vio_cmo_alloc(9) — ngl, it's giving main character energy 💅. This one is all about allocating IO memory for CMO-enable devices, and it's lowkey iconic. No cap.

🌸 NAME 🌸

vio_cmo_alloc — allocate IO memory for CMO-enable devices ✨

🎀 SYNOPSIS 🎀

int vio_cmo_alloc (struct vio_dev *viodev , size_t size );

🦋 ARGUMENTS 🦋

• viodev — VIO device requesting IO memory 👑
• size — size of allocation requested 🍓

💖 DESCRIPTION 💖

okay so here's the tea ☕: allocations come from memory reserved for the devices and any excess IO memory available to all devices. and the way that the spare pool used to service hotplug must be equal to VIO_CMO_MIN_ENT for the excess pool to be made available? obsessed 🫶.

Return codes, bestie: 0 for successful allocation and -ENOMEM for a failure 😭.

🌈 SEE ALSO 🌈

Kernel file ./arch/powerpc/platforms/pseries/vio.c — and the whole squad is here, fr fr:

• vio_cmo_dealloc(9)
• vio_cmo_entitlement_update(9)
• vio_cmo_balance(9)
• vio_cmo_set_dev_desired(9)
• vio_cmo_bus_probe(9)
• vio_cmo_bus_remove(9)
• vio_cmo_bus_init(9)
• vio_h_cop_sync(9)
• vio_match_device(9)
• vio_unregister_driver(9)
• vio_register_device_node(9)
• vio_bus_init(9)
• vio_get_attribute(9)
• vio_find_node(9)

okay bye bestie 🫶 this page comes from ./arch/powerpc/platforms/pseries, dated October 2026, and it's the vio_cmo_alloc(9) entry — periodt 💅✨