bhyve vmm ops could have stronger guardrail
When bhyve is initialized, it chooses a
vmm_ops set, based on the physical CPU (Intel or AMD) it's running on. The macros which call into this struct have explicit checks for it being non-NULL, which should never be possible given our guards anyways. To simplify those macros and maintain the safety, we could populate a null-ish
vmm_ops struct with functions that simply panic.
Updated by Electric Monk almost 2 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
commit b38fc3ed80ecaf16c46433e690e6f17495c5e179 Author: Patrick Mooney <firstname.lastname@example.org> Date: 2020-07-13T17:20:06.000Z 12922 bhyve vmm ops could have stronger guardrail Reviewed by: Andy Fiddaman <email@example.com> Reviewed by: Mike Zeller <firstname.lastname@example.org> Approved by: Dan McDonald <email@example.com>