-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add the VMM Communication Exception (#VC) to the InterruptDescriptorTable #313
Add the VMM Communication Exception (#VC) to the InterruptDescriptorTable #313
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, looks good to me! I tried to improve the docs a bit, please let me know what you think.
…able For AMD SEV-ES and SEV-SNP, handling this exception is crucial for functionality. Signed-off-by: Harald Hoyer <[email protected]> Co-authored-by: Philipp Oppermann <[email protected]>
88dc20c
to
a1fd7c3
Compare
cc @josephlr |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for the delay. Looks good, thanks a lot!
This is not covered on the online docs? |
@Zildj1an so I see this documented at: https://docs.rs/x86_64/latest/x86_64/structures/idt/struct.InterruptDescriptorTable.html#structfield.vmm_communication_exception There's also an enum value defined here: https://docs.rs/x86_64/latest/x86_64/structures/idt/enum.ExceptionVector.html#variant.VmmCommunication Were you expecting to find it documented somewhere else? |
For AMD SEV-ES and SEV-SNP, handling this exception is crucial for functionality.
Signed-off-by: Harald Hoyer [email protected]