vio_cmo_entitlement_update(9)

💅 vio_cmo_entitlement_update(9) 💅

okay so bestie, welcome to the Kernel API Manual ✨ this page is all about vio_cmo_entitlement_update, and it is literally here to manage system entitlement changes 🎀

---

✨ NAME ✨

vio_cmo_entitlement_update — Manage system entitlement changes. That's the whole name vibe, no cap 💅

---

🌸 SYNOPSIS 🌸

here's the signature, copied exactly because we do not play with code 🫶

int vio_cmo_entitlement_update (size_t new_entitlement );

---

🎀 ARGUMENTS 🎀

• new_entitlement — the new system entitlement to attempt to accommodate. That's the one argument, bestie 💖

---

💖 DESCRIPTION 💖

okay so here's the tea ☕: increases in entitlement will be used to fulfill the spare entitlement, and the rest is given to the excess pool. Decreases, if they are possible, come from the excess pool and from unused device entitlement. That's literally the flow 🔥

---

🔥 RETURN 🔥

• 0 — on success, slay 💅
• -ENOMEM — when change can not be made 😭

---

🌈 SEE ALSO 🌈

Kernel file: ./arch/powerpc/platforms/pseries/vio.c — and here's the whole squad, all of them, no skips 👑

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

---

mwah 💋 final vibe: this page lives in ./arch/powerpc/platforms/pseries, dated October 2026, and it's vio_cmo_entitlement_update(9). periodt ✨