clarify VMCB interface in bhyve
Similar to #13063, the in-kernel interface used by bhyve to access the VMCB on AMD hardware could be cleaned up. Failed register identification checks should be fatal when the consumer is in-kernel (and therefore expected to operate on valid registers). Making this consistent will simplify later work to expose more of the VM state to userspace.
Updated by Patrick Mooney 6 months ago
With this change in place, all of the usual suspects were booted up:
All started up and ran fine. I dtraced the new vmcb_* functions to verify that the BE was correctly updated and the updated code paths were being utilized.
Updated by Electric Monk 6 months ago
- Status changed from In Progress to Closed
- % Done changed from 0 to 100
commit 096bb5cb663d8fa04eda9a4aceb4d82a9cbae42c Author: Patrick Mooney <firstname.lastname@example.org> Date: 2020-09-02T20:24:18.000Z 13072 clarify VMCB interface in bhyve Reviewed by: Robert Mustacchi <email@example.com> Reviewed by: Mike Zeller <firstname.lastname@example.org> Approved by: Dan McDonald <email@example.com>