dc_get_qos_info(9)

✨ dc_get_qos_info — the QoS tea spilling function ✨

okay bestie, so this is a Kernel API Manual page for dc_get_qos_info(9), and it's literally the function that goes and asks the display core "hey girl, what's your QoS looking like?" 💅 Let's get into it.

---

🌸 NAME 🌸

dc_get_qos_info — retrieve Quality of Service (QoS) information from display core 🎀

---

🦋 SYNOPSIS 🦋

bool dc_get_qos_info (struct dc *dc , struct dc_qos_info *info );

---

💖 ARGUMENTS 💖

• dc — the DC context that's holding your current display configuration ✨
• info — a pointer to the dc_qos_info structure you want populated with all the QoS metrics 🫶

---

👑 DESCRIPTION 👑

So basically, this function pulls QoS metrics out of the display core, and benchmark tools can use those metrics to analyze how the display system is performing. 🔥 Heads up though: it may take several milliseconds to run because the hardware has to actually do measurement stuff. Not instant, no cap. 😭

The QoS info it gives you includes:

• Bandwidth bounds (the lower limits, in Mbps) 💜
• Latency bounds (the upper limits, in nanoseconds) ⭐
• Hardware-measured bandwidth metrics (peak/average, in Mbps) 🌈
• Hardware-measured latency metrics (maximum/average, in nanoseconds) 🦋

The function populates the dc_qos_info structure you pass in with the current QoS measurements. But — and this is the important part, bestie — if the hardware measurement functions aren't available for the current DCN version, the function returns false and the info structure is zero'd. 🙈 So like, check that return value, fr fr.

---

🔥 RETURN 🔥

• true — QoS information was successfully retrieved, slay 💅
• false — the measurement functions are unavailable, or the hardware measurements just couldn't be performed 😭

---

🧚 SEE ALSO 🧚

Kernel file ./drivers/gpu/drm/amd/display/dc/dc.h — plus the whole friend group: MAX_SURFACES(9), MAX_PLANES(9), color-management-caps(9), struct rom_curve_caps(9), struct dpp_color_caps(9), struct mpc_color_caps(9), struct dc_color_caps(9), enum pipe_split_policy(9), dc_check_state_update(9), dc_update_state(9), dc_update_state_init(9), dc_update_state_prepare(9), dc_update_state_execute(9), dc_update_state_cleanup(9), struct dc_probe_latencies(9), struct dc_probe_status(9), enum dc_get_status_type(9), struct dc_get_status_options(9), struct dc_state_status(9), dc_state_get_status(9), struct dc_validation_stream(9), struct dc_validation_set(9), dc_get_underflow_debug_data_for_otg(9), dc_capture_register_software_state(9), dc_override_memory_bandwidth_request(9) ✨

---

💀 reminder: the display core lives at ./drivers/gpu/drm/amd/display/dc, and this page is from the October 2026 drop. iykyk. 🫶

aaand that's the whole page, bestie — dc_get_qos_info(9), straight from the October 2026 manual, living in ./drivers/gpu/drm/amd/display/dc. go get those QoS metrics, you icon 👑💖