Initial vmx PR

[betahxy]

Summary of this Pull Request (PR)

Add description here.

Intent for your PR

Choose one (Mandatory):

• [ ] This PR is for a code-review and is intended to get feedback, but not to be pulled yet.
• [x] This PR is mature, and ready to be integrated into the repo.

Reviewers (Mandatory):

(Specify @<github.com username(s)> of the reviewers. Ex: @user1, @user2)

Code Quality

As part of this pull request, I've considered the following:

Style:

• [x] Comments adhere to the Style Guide (SG)
• [x] Spacing adhere's to the SG
• [x] Naming adhere's to the SG
• [x] All other aspects of the SG are adhered to, or exceptions are justified in this pull request
• [ ] I have run the auto formatter on my code before submitting this PR (see doc/auto_formatter.md for instructions)

Code Craftsmanship:

• [x] I've made an attempt to remove all redundant code
• [x] I've considered ways in which my changes might impact existing code, and cleaned it up
• [x] I've formatted the code in an effort to make it easier to read (proper error handling, function use, etc...)
• [x] I've commented appropriately where code is tricky
• [x] I agree that there is no "throw-away" code, and that code in this PR is of high quality

Testing

I've tested the code using the following test programs (provide list here):

• [ ] micro_booter
• [x] unit_pingpong
• [x] simple_vmm
• [ ] unit_schedtests
• [ ] ...(add others here)

[gparmer]

Once @esmakokten accepts the invite to be part of the researchers team for gwsystems, lets assign her as a reviewer.

[gparmer]

I didn't realize that you were going to PR so much more than the VMX stuff. This will take a while to review for the expanded review. Can you provide a list of files/directories that @davidbabono and @esmakokten could focus on related to the VMX/VMM stuff? I'd like them to be able to ignore much of the PR that is beyond that scope.

[betahxy]

I didn't realize that you were going to PR so much more than the VMX stuff. This will take a while to review for the expanded review. Can you provide a list of files/directories that @davidbabono and @esmakokten could focus on related to the VMX/VMM stuff? I'd like them to be able to ignore much of the PR that is beyond that scope.

Sorry for the confusion, but in order to PR to the main branch, it has to include the previous MPK commits that you've reviewed. I've fixed all the compiling warnings I could see when building the system, which is trying to follow the previous review.

@gparmer @esmakokten @davidbabono And, for this PR of VMX, I think these directories should be more focused on:

1. src/platform/x86_64/vmx: this is where the kernel's support of vmx.
2. src/components/lib/vmrt: this is where the user level vm runtime lib that creates necessary resources for running a vm.
3. src/components/implementation/simple_vmm: this is the VMM component that tries to use vmrt lib to create and run a simple vm.

However, there is some additional code that is necessary such as capmgr, which is necessary to create vm resources like capabilities. But this part is less interesting.

[gparmer]

Great, thanks @betahxy! It might take a little while to get a review done, but we'll get it done ASAP! Very much appreciated for all of this work.