pm_qos_update_target(9)

💅 pm_qos_update_target 💅

okay so bestie, welcome to the Kernel API Manual, section 9 — this is the page for pm_qos_update_target, and it's genuinely one of those little functions that's doing a LOT behind the scenes. PM QoS constraint request list maintenance, but make it cute. 🎀

---

✨ NAME ✨

pm_qos_update_target — update a list of PM QoS constraint requests. that's it, that's the whole vibe. 💖

---

🌸 SYNOPSIS 🌸

int pm_qos_update_target (struct pm_qos_constraints *c , struct
plist_node *node , enum pm_qos_req_action action , int value );

---

🦋 ARGUMENTS 🦋

• c — the list of PM QoS requests you're working with. this is the main character list, bestie. 👑
• node — the target list entry. the specific lil plist node you're here to fuss over. ✨
• action — what you're actually doing to it: add, update or remove. pick one, no cap. 💅
• value — the new request value for the target list entry. the number that's about to be somebody's whole personality. 🔥

---

🌈 DESCRIPTION 🌈

so here's the tea: this function updates the given list of PM QoS constraint requests, c, by carrying out an action that involves the node list entry and the value on it. like, it's doing the work on that one specific node inside that one specific list. periodt. 💜

the recognized values of action are literally these three, and you need to know all of them:

• PM_QOS_ADD_REQ — store value in node and add it to the list. she's new here and she's arriving with data. 🦋
• PM_QOS_UPDATE_REQ — remove node from the list, store value in it, and add it to the list again. yes, she leaves and comes back hotter. iconic behavior tbh. 🔥
• PM_QOS_REMOVE_REQ — remove node from the list and ignore value. goodbye, we don't need the number, we just need you GONE. 💀

ngl, that middle one is doing an entire round trip just to change a value, but that's genuinely what the manpage says, so we respect it. 🫶

---

⭐ RETURN ⭐

1 if the aggregate constraint value has changed, 0 otherwise. so basically: did the overall constraint number shift? yes or no. that's the whole return. simple, clean, slay. ✨

---

🧚 SEE ALSO 🧚

the reading list, bestie — go read these next, iykyk:

• kernel file ./kernel/power/qos.c
• pm_qos_read_value(9)
• pm_qos_flags_remove_req(9)
• pm_qos_update_flags(9)
• cpu_latency_qos_limit(9)
• cpu_latency_qos_request_active(9)
• cpu_latency_qos_add_request(9)
• cpu_latency_qos_update_request(9)
• cpu_latency_qos_remove_request(9)
• cpu_wakeup_latency_qos_limit(9)
• freq_constraints_init(9)
• freq_qos_read_value(9)
• freq_qos_apply(9)
• freq_qos_add_request(9)
• freq_qos_update_request(9)
• freq_qos_remove_request(9)
• freq_qos_add_notifier(9)
• freq_qos_remove_notifier(9)

---

and that's the page!! 🎀 this one came out of ./kernel/power and it's dated October 2026 — so go forth, update your QoS targets, and remember: the aggregate constraint value changing is the only thing that gets you a 1. mwah 💋🌸