bhyve kernel/user split should be clearer
To avoid code duplication, and for convenience, bhyve shares swaths of logic between the kernel module and userspace. For certain things, like ioctl struct definitions, this is obviously a necessity. In other cases, it's just to provide consistent API expectations for kernelspace and userspace code. In the latter case, some of the demarcation lines can be confusing, and it introduces unnecessary coupling between the userland and kernel code. Where possible, it would be nice to separate those interfaces.
Note: The instruction decoding logic is used in both kernel and userland components and its separation is complicated beyond the scope of this change.
Updated by Electric Monk 5 months ago
- Status changed from In Progress to Closed
- % Done changed from 0 to 100
commit b58b977e8fdb738e19dfe72999e4f57a62e9d05f Author: Patrick Mooney <email@example.com> Date: 2020-06-23T16:07:07.000Z 12869 bhyve kernel/user split should be clearer Reviewed by: Mike Zeller <firstname.lastname@example.org> Approved by: Dan McDonald <email@example.com>