Skip to content

configurable CPU topology - #1237

Open
iximeow wants to merge 7 commits into
masterfrom
cpu-topology
Open

iximeow wants to merge 7 commits into
masterfrom
cpu-topology

Conversation

@iximeow

@iximeow iximeow commented Oct 30, 2026

Copy link
Copy Markdown
Member

this moves a VM's apparent CPU topology into the propolis-server API (and makes it more configurable in propolis-standalone as well). this is really intended as a stepping stone for all of: more explicit CPU pinning directives based on control plane CPU selection, CCX-aware CPU placement, getting Propolis a bit out of the way of >254 vCPU work, and, most excitingly to me, closing VMs should not have vCPU-many sockets.

realistically this is a demonstrator for another change I'll have up against Omicron in a bit here to select a new virtual platform which has as a detail more reasonable CPU topology.

it's also full of TODOs and could use at least one (1) test that on AMD the guest gets a topology we'd want it to get, instead of single-thread sockets.

most of the owl for CPU topology. at least three circles.
@iximeow iximeow mentioned this pull request Oct 30, 2026
2 tasks
@iximeow
iximeow marked this pull request as ready for review November 17, 2026 17:18
@iximeow

iximeow commented Nov 17, 2026

Copy link
Copy Markdown
Member Author

this actually does the needful now and would be something I'm willing to merge, but the conflicts of course need addressing. even if rebased this will conflict with #1217 on account of the API changes, so we should probably get that in, then I'll get this in, and then we can do a new ACPI type in the API to set up X2APIC structs over there too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant