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.
Sources:
Linux kernel mailer, via Phoronix
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.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.
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.


33 Comments on Linux Kernel Gets AMD Capacity-Aware Scheduling for Zen 6 Heterogeneous CPU Architectures
Let's be clear, Zen cores don't have any L3 cache. They only have L1 and L2, in which, c cores are identical to normal ones.
L3 cache is added to the CPU as a whole. The 8500G, for example, has 16 MB with a mixed 2x Zen 4 + 4x Zen 4c core config. The 8700G has also 16 MB, but with 8 Zen 4 cores. If you look at it from here, the Zen 4 cores in the 8700G have less L3 than the Zen 4c ones in the 8500G.
L3 to core is a ratio, not attachment.
Look at this block diagram, it'll make sense:
The L3 cache is a separate entity that any and all cores can use. I hope this makes sense.
Let me reiterate: Zen cores do not have any L3 cache in them.
Did you even read the article you’re posting in?
Unlike AMD Intel ties L3 to cores so higher core count CPUs have but it's still all shared.
Snark is pathetic in general but doubly so when you're the one who's wrong.
That said, I agree that this looks like they are getting ready for mixed SIMD support (otherwise CPPC2 would already be handling everything fine), which I am not a fan of.
All it takes is one scheduler mistake to cause a pile of headaches, like early days with Adler Lake, where AVX-512 could be enabled on the P-cores, but was not supported on the E-cores...
Seriously guys, read up on it.
Because CPPC2 already handles this otherwise?
AMD64 Architecture Programmer’s Manual Volume 2: System Programming
Section 17.6 is dedicated to CPPC, and 17.6.4 describes CPPC Performance Levels and Capabilities.
Assuming the cores offer identical SMID support (same capabilities, not necessarily the same performance!), as I understand the implementation, CPPC2 covers nearly every use case I can think of.
The only thing missing is scheduler hints for mixed SMID support, which is the point of the new CAS.
"C" cores aren't new. If they were any different from normal ones in their functioning, then AMD would have pulled something like this long ago, as CPPC just wouldn't have cut it.
Up until Zen 6/6c, the Compact Cores had identical L1 and L2 cache sizes, but had less (L3 Cache)/(Cores in Complex).
One could argue that, pre-Zen 6c, this means less L3 cache avaliable for each core, which is correct.
The difference is that L1 and L2 are inherent to the core, while L3 is shared between cores.
Put otherwise, a core is not a core without the L1 and L2 caches (which is identical between Standard and Compact cores), with the L3 cache being external to the cores.
It is a bit more complex than this, though, as the cores are not limited to a small slice of L3, and a single core under the right conditions could use the full L3.
For those unsure, perhaps you can better see here what is meant.
In the first graphic, you can see that both the Zen 4 and Zen 4c cores have the L1 and L2 caches inherently contained within the individual cores.
In the second graphic, the 16MB shared L3 is clearly shown as being external to the individual cores.
Similarly, my car's 4:1 wheel to engine ratio doesn't mean that there are 4 wheels in its engine somewhere.
But yeah, 6 core parts have a higher L3 per core ratio. People: think about it. ;)