Linux kernel 7.2 has shipped after more than a year of scheduler development, headlined by Cache Aware Scheduling behind the CONFIG_SCHED_CACHE option, which groups related tasks onto cores sharing the same last-level cache instead of scattering them across zones. AMD platform drivers gain Zen 6 preparation work, HFI v3 ranking tables, and AMDGPU picks up initial HDMI 2.1 Fixed Rate Link support years after the HDMI Forum blocked it from open source drivers. Intel EDAC work targets upcoming Diamond Rapids Xeons, TDX modules can now update at runtime without a reboot, and Apple M3 MacBooks can boot the mainline kernel for the first time via Asahi Linux efforts, albeit only to a serial console. Other additions include Btrfs large folio support leaving experimental status, a new USB4STREAM protocol, and broader laptop hardware support.
Questions this post answers
What does Cache Aware Scheduling do in Linux kernel 7.2?
Cache Aware Scheduling, merged in Linux kernel 7.2 after more than a year of development behind the CONFIG_SCHED_CACHE option, groups related tasks onto cores sharing the same last-level cache (LLC) instead of letting the scheduler scatter them across cache zones on chips with multiple LLCs. This reduces cache misses and improves performance on multi-cache-domain processors. Track scheduler changes like this on daily.dev before rebuilding kernels for performance-sensitive workloads.
Can Apple M3 MacBooks boot Linux now?
Apple M3 MacBooks can boot the mainline Linux kernel for the first time as of kernel 7.2, though currently only to a serial console rather than a full desktop environment. This milestone was delivered through the work of Asahi Linux developers who have been porting Linux to Apple Silicon hardware. Developers eyeing Apple Silicon Linux support can follow progress like this on daily.dev.
Why did AMDGPU take years to get HDMI 2.1 support in the open source driver?
AMDGPU gained initial HDMI 2.1 Fixed Rate Link (FRL) support in Linux kernel 7.2, years after the HDMI Forum blocked the feature from being implemented in open source drivers. The delay stemmed from licensing restrictions imposed by the HDMI Forum rather than technical limitations on AMD's side. Keep up with open source driver and licensing disputes like this via daily.dev.