Project

General

Profile

Actions

Bug #12922

closed

bhyve vmm ops could have stronger guardrail

Added by Patrick Mooney almost 2 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
Low
Category:
bhyve
Start date:
Due date:
% Done:

100%

Estimated time:
Difficulty:
Medium
Tags:
Gerrit CR:

Description

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.

Actions

Also available in: Atom PDF