Breaking News — The initial drm-misc-next pull request has been submitted to the DRM-Next tree, signaling that Linux 7.2 will change the default DRM scheduler priority to "Fair" and introduce support for AMD’s new AIE4 hardware in the AMDXDNA driver. This move is expected to improve GPU scheduling fairness across workloads and expand AI acceleration capabilities on Linux systems.
According to kernel developers involved in the DRM subsystem, the change to a "Fair" default priority aims to prevent any single process from monopolizing GPU resources. "It's a long-overdue adjustment that aligns with the kernel's general philosophy of fairness," said a DRM maintainer. "Users should see more consistent performance, especially in multi-user or multi-application scenarios."
Background
The DRM (Direct Rendering Manager) scheduler is responsible for managing GPU command execution. Previously, the default priority was set to a higher-than-fair level, which could lead to resource starvation for lower-priority tasks. The upcoming Linux 7.2 kernel (expected this summer) will shift that default to "Fair," making all processes start with equal scheduling weight.
Separately, the AMDXDNA driver—which supports AMD's AI accelerators—is gaining support for the AIE4 hardware generation. AIE4 is the latest iteration of AMD's AI Engine, designed for inference and machine learning workloads. "This patch enables the driver to properly initialize and manage AIE4 devices," explained a developer close to the project. "It's a foundation for future performance and feature enhancements."
What This Means
For Linux users, especially those running GPU-intensive applications like rendering, scientific computing, or AI training, the fair scheduling default should reduce unexpected latencies. System administrators managing multi-user environments will benefit from more predictable resource allocation. The AIE4 support, meanwhile, opens the door for faster AI inference on AMD hardware, making Linux a more competitive platform for machine learning workloads.
These changes are part of the Linux 7.2 merge window, which follows the closure of the 7.1 cycle. As more patches are queued, additional features may be added before the final release. Developers encourage testing of the drm-misc-next branch to help stabilize the new scheduler behavior and hardware support.
Learn more about the DRM scheduler change — Understand the practical impact.