vio_cmo_set_dev_desired(9)

💅 vio_cmo_set_dev_desired(9) — Kernel API Manual energy 💅

okay bestie, we’re in the Kernel API Manual and this page is literally all about vio_cmo_set_dev_desired(9). no cap, it’s a tiny one but it matters 💖

---

🌸 NAME 🌸

vio_cmo_set_dev_desired — set the desired entitlement for a device ✨

---

✨ SYNOPSIS ✨

void vio_cmo_set_dev_desired (struct vio_dev *viodev , size_t desired );

---

🎀 ARGUMENTS 🎀

• viodev — the struct vio_dev for the device you wanna alter 🫶
• desired — the new desired entitlement level, in bytes 💅

---

🦋 DESCRIPTION 🦋

This one is for devices to request a change to their entitlement at runtime, or through sysfs. iconic behavior, honestly 🌈

The desired entitlement level gets changed, and then a balancing of system resources is scheduled to run in the future. so like, the vibe check is queued up for later ⭐

---

🔥 SEE ALSO 🔥

Kernel file: ./arch/powerpc/platforms/pseries/vio.c 👑

the whole squad:

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

---

this page came from the ./arch/powerpc/platforms/pseries part of the tree, dated October 2026 — and that’s the cute lil sign-off, bestie 🎀💖✨