Additional firmware configuration via IGVM #191
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Jon Lange <jlange@microsoft.com>
Signed-off-by: Jon Lange <jlange@microsoft.com>
Signed-off-by: Jon Lange <jlange@microsoft.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change introduces additional configuration information in the IGVM to support firmware other than OVMF. In particular, it permits the firmware to live at the base of the address space instead of the ROM area; it permits the guest to configure initial context state that differs from the processor's architected reset state; and it permits the guest to enable vTOM in accordance with the vTOM policy described to the loader by the IGVM file.