AMD’s reported Linux Capacity-Aware Scheduling (CAS) proposal has two patches: one would let amd-pstate publish per-CPU capacity differences to the scheduler, and the other would make amd-hfi stand aside while CAS is active. In a report published November 17, 2026, Pause Hardware described the changes as a proposal, not as support already integrated into Linux.

The key change would be what the scheduler knows about each CPU: the proposal concerns capacity information, not a new setting available to try in a released kernel.

What would the two patches change?

The first patch would have amd-pstate publish asymmetric per-CPU capacities through the hybrid-architecture capacity-scaling interface. Pause Hardware says the driver does not currently expose per-CPU capacity to the scheduler, which treats cores as equivalent for that criterion. Sharing the differences would let the scheduler account for CPU capacity when placing tasks.

The second patch would make amd-hfi stand aside while CAS is active. Pause Hardware says both mechanisms act on the same scheduler state, so the proposal coordinates their behavior rather than having them act on that state at the same time.

The proposed design is described as enabled by default on compatible hardware, with amd_cas=disable as a boot-time opt-out. That parameter is part of the reported proposal.

Which AMD processors does the report mention?

Pause Hardware identifies some Hawk Point processors combining Zen 4 and Zen 4c as relevant to the proposal. The reported example does not name particular models, so it does not identify a complete set of processors that would support CAS.

Does the proposal confirm Zen 6 LP?

No. Pause Hardware discusses Zen 6 LP as a rumor; the CAS proposal does not confirm those cores or establish their specifications or practical performance and power effects.