Page MenuHomeFreeBSD

bhyve: Remove vestigial support for setting max vCPUs.
ClosedPublic

Authored by jhb on Oct 27 2022, 3:06 PM.
Tags
None
Referenced Files
F82015946: D37176.id.diff
Wed, Apr 24, 2:07 PM
F82015942: D37176.id123101.diff
Wed, Apr 24, 2:07 PM
F82015776: D37176.id112285.diff
Wed, Apr 24, 2:03 PM
Unknown Object (File)
Sun, Apr 21, 8:17 PM
Unknown Object (File)
Tue, Apr 9, 4:12 PM
Unknown Object (File)
Feb 15 2024, 6:02 AM
Unknown Object (File)
Feb 15 2024, 4:05 AM
Unknown Object (File)
Feb 15 2024, 4:05 AM

Details

Summary

The kernel part of the hypervisor is not going to support per-VM
maxcpu limits. The topology is only used to control the values
returned by CPUID leaves for which max vCPUs is not relevant.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

jhb requested review of this revision.Oct 27 2022, 3:06 PM
jhb retitled this revision from bhyve: Remove vestigal support for setting max vCPUs. to bhyve: Remove vestigial support for setting max vCPUs..Nov 3 2022, 11:14 PM
This revision is now accepted and ready to land.Nov 4 2022, 6:43 AM

Should vm_set_topology() be updated to indicate that maxcpus is unimplemented? I can see why you didn't remove the parameter at least.

I may actually wait on this. It might still be useful to set the size of the maxcpus array by passing the limit in via a new vmm_create operation.

I don't care. It's unused code, so we can remove it. If you like to add support to vm_create for maxcpus, you can easily revert this change. OTOH, it's fine to keep it as it is.

I guess it's fine to merge.