Monday, November 16th 2026

Linux Kernel Gets AMD Capacity-Aware Scheduling for Zen 6 Heterogeneous CPU Architectures

It has long been rumored that AMD is working on new Zen 6 LP cores for its next-gen Zen 6 (see our Zen 6 Technical Deep Dive here) CPU architecture—which has already been unveiled for server applications—and it now appears as though the Linux kernel is being prepared to support that new architecture across the board. A patch series by AMD itself details support for a Capacity-Aware Scheduling, which would effectively allow the Linux kernel to detect the capabilities of each individual CPU core and assign work to that CPU core accordingly.
Amd-pstate does not export per-CPU capacity today, so the scheduler treats all cores as equal and places tasks without regard to core strength.
Patch 1 makes amd-pstate publish asymmetric per-CPU capacities via the arch hybrid capacity scaling interface. It is enabled by default on supported hardware and can be turned off with the "amd_cas=disable" boot parameter.
Patch 2 makes amd-hfi stand down when CAS is active, since both manage the same scheduler state.
Capacity-aware scheduling would enable Capacity-Aware Scheduling on all AMD heterogeneous CPUs on Linux, which means going back to certain CPUs in the Hawk Point family, which combined Zen 4 and Zen 4c CPUs. The fact that AMD has waited so long to introduce CAS also might suggest that the new Zen 6 LP CPU cores are significantly less capable and thus significantly less power-hungry than the regular Zen 6 cores.
Sources: Linux kernel mailer, via Phoronix
Add your own comment

33 Comments on Linux Kernel Gets AMD Capacity-Aware Scheduling for Zen 6 Heterogeneous CPU Architectures

#26
outlw
AusWolfSimilarly, my car's 4:1 wheel to engine ratio doesn't mean that there are 4 wheels in its engine somewhere.
🤔

Posted on Reply
#27
user556
And that ratio came from observations on the server grade CPUs that have pure Zen 4C/5C chiplets. It's a bit meaningless for APUs using mixed cores with a single common L3 cache.

Amusingly, the Zen 6C chiplets that have been flogged to AI data centres in the last few months have the L3 cache ratio the same 4 MB per core as the fat Zen 6 chiplets. And given there is 32 6C cores on each chiplet, that makes 128 MB of L3 per chiplet.
Posted on Reply
#28
GenericUsername2001
To add to this fun discussion, for Zen 6 the "c" cores are a bit different internally from the regular Zen 6 cores when it comes to their out-of-order handling hardware; they aren't just lower clock versions with the stuff needed to support higher frequencies stripped out to save die space. Chips and Cheese has a good breakdown. chipsandcheese.com/p/amds-zen-6-family-feeding-the-beast

Note that is for the server chiplets; it will be interesting to see if AMD keeps those minor changes on the laptop APU chips that use both Zen 6 and Zen 6c cores.
Posted on Reply
#29
jpvalverde85
An scheduler for heterogeneous cores? That's kinda software that does the same as the Intel Thread Director. It could be of relevance to maximize performance over all over the place, but there is more to gain on very dense cpus.
Posted on Reply
#30
kazuviking
outlwlike early days with Adler Lake, where AVX-512 could be enabled on the P-cores, but was not supported on the E-cores...
There was no headache as enabling AVX-512 disabled the E cores entirely in bios.
Posted on Reply
#31
outlw
kazuvikingThere was no headache as enabling AVX-512 disabled the E cores entirely in bios.
It has been a while, but as I recall it, at least with the early BIOS', this was not always the case.
I am pretty sure AVX-512 support was completely removed by Intel from later BIOS releases.
Posted on Reply
#32
user556
outlwIt has been a while, but as I recall it, at least with the early BIOS', this was not always the case.
I am pretty sure AVX-512 support was completely removed by Intel from later BIOS releases.
I know that the 12400F is still a big seller (For Intel) to this day. And has been the top selling Intel part most of its life. It has six P-cores, no E-cores enabled.

Given the many newer parts to chose from, but no others without E-cores, I read that as an indictment on E-cores. Whether that also mean AVX-512 is used, I can't really say. I guess it's more chosen for decent gaming at low price.
Posted on Reply
#33
kazuviking
outlwI am pretty sure AVX-512 support was completely removed by Intel from later BIOS releases.
It wasn't, intel physically fused off AVX-512 from later production alderlake. Most motherboards still allows you to turn it on.
Posted on Reply
Add your own comment
Nov 18th, 2026 09:47 CST change timezone

New Forum Posts

Popular Reviews

TPU on YouTube

Controversial News Posts