vio_cmo_bus_init(9)

💖 NAME 💖

vio_cmo_bus_init — CMO entitlement initialization at bus init time ✨

Hiii bestie 🫶 you're looking at vio_cmo_bus_init(9) from the Kernel API Manual, and it's giving tiny init-time setup icon energy.

🌸 SYNOPSIS 🌸

void vio_cmo_bus_init (void );

🎀 ARGUMENTS 🎀

• void — no arguments. Not a single one. Zero. Nada. This function said “I need no input, I’m built different” 💅.

🦋 DESCRIPTION 🦋

Okay so here’s the vibe: vio_cmo_bus_init sets up the reserve and excess entitlement pools. It works that setup out based on the available system entitlement and based on the number of devices in the OF tree that require entitlement in the reserve pool. That’s it, that’s the whole lore — bus-init-time CMO entitlement initialization, slay ✨.

🌈 SEE ALSO 🌈

Kernel file ./arch/powerpc/platforms/pseries/vio.c — plus the whole friend group:

• vio_cmo_alloc(9)
• 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_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)

And that’s the page, bestie 🎀 it comes from ./arch/powerpc/platforms/pseries, dated October 2026, and signs off as vio_cmo_bus_init(9) — mwah 💋✨.