[vmm] refactor vmm builder code to separate the architecture dependent code in their own modules #4411
Labels
Good first issue
Indicates a good issue for first-time contributors
Priority: Low
Indicates that an issue or pull request should be resolved behind issues or pull requests labelled `
Status: Parked
Indicates that an issues or pull request will be revisited later
Description
The
vmm
crate hosts most of the modules that implement the Firecracker functionality. Moreover, at its "top-level", mainlylib.rs
andbuilder.rs
includes the logic for creating theVmm
the object that describes a Firecracker microVM. The logic for creatingVmm
objects is divided betweenlib.rs
andbuilder.rs
. Moreover, this functionality includes a lot of architecture specific code that has been gathered along the years to a code-base the logic of which is hard to follow "sometimes".Action Items
A nice way to refactor this (and hopefully make it less painful to follow), would be to isolate the logic for building the
Vmm
in its own module and isolate the architecture specific code in their own sub-modules, one for each architecture.Acceptance criteria
Vmm
objectThe text was updated successfully, but these errors were encountered: