xe_pm_runtime_get_ioctl(9)

💖 xe_pm_runtime_get_ioctl(9) 💖

okay bestie, welcome to the Kernel API Manual page for xe_pm_runtime_get_ioctl — yes, the function name is also the title, we love a self-referential moment ✨.

🌸 NAME 🌸

xe_pm_runtime_get_ioctl — Get a runtime_pm reference before ioctl 💅

✨ SYNOPSIS ✨

int xe_pm_runtime_get_ioctl (struct xe_device *xe );

🎀 ARGUMENTS 🎀

• xe — xe device instance 🫶

🦋 DESCRIPTION 🦋

So here’s the tea, bestie: when possible, scope-based runtime PM (through ACQUIRE(xe_pm_runtime_ioctl, ...)) is preferred over direct usage of this function. No cap, scope-based is the main character when it fits.

Manual get/put handling should only be used when the function contains goto-based logic which can break scope-based handling, or when the lifetime of the runtime PM reference does not match a specific scope (e.g., runtime PM obtained in one function and released in a different one). That’s the whole vibe check: manual handling is for those specific situations, not just because you feel like it 🙈.

🔥 RETURN 🔥

Any number greater than or equal to 0 for success, negative error code otherwise. Slay 💅.

🌈 SEE ALSO 🌈

the whole squad is here, no one left behind:

• Kernel file ./drivers/gpu/drm/xe/xe_pm.c Xe Power Management(9)
• xe_pm_might_block_on_suspend(9)
• xe_pm_block_on_suspend(9)
• xe_rpm_reclaim_safe(9)
• xe_pm_suspend(9)
• xe_pm_resume(9)
• xe_pm_init_early(9)
• xe_pm_probe(9)
• xe_pm_init(9)
• xe_pm_fini(9)
• xe_pm_runtime_suspended(9)
• xe_pm_runtime_suspend(9)
• xe_pm_runtime_resume(9)
• xe_pm_runtime_get(9)
• xe_pm_runtime_put(9)
• xe_pm_runtime_get_if_active(9)
• xe_pm_runtime_get_if_in_use(9)
• xe_pm_runtime_get_noresume(9)
• xe_pm_runtime_resume_and_get(9)
• xe_pm_assert_unbounded_bridge(9)
• xe_pm_set_vram_threshold(9)
• xe_pm_d3cold_allowed_toggle(9)
• xe_pm_module_init(9)

mwah 💋 this cutie lives in ./drivers/gpu/drm/xe, is dated October 2026, and is filed under xe_pm_runtime_get_ioctl(9) — periodt 🫶