-
Notifications
You must be signed in to change notification settings - Fork 3
Vmsa ovmf #10
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
Vmsa ovmf #10
Conversation
The upstream kernel introduced[^1] a new IOCTL called KVM_SEV_INIT2 which expects some floating point registers to be set to a value other than zero. Because of these adjustments, we needed to update the VMSA structure to match this. [^1]: [https://lore.kernel.org/kvm/[email protected]/](https://lore.kernel.org/kvm/[email protected]/) With KVM_SEV_INIT2, rather than 0, QEMU/KVM will instead begin setting the following fields in the VMSA before measurement/encryption: VMSA byte offset [1032:1033] = 80 1f (MXCSR, Multimedia Control Status Register) VMSA byte offset [1040:1041] = 7f 03 (FCW, FPU/x86 Control Word) Setting FCW (FPU/x86 Control Word) to 0x37f is consistent with 11.5.7 of APM Volume 2. MXCSR reset state is not defined for XSAVE, but QEMU's 0x1f80 value is consistent with machine reset state documented in APM Volume 2 4.2.2. As such, it is reasonable to begin including these in the VMSA measurement calculations. Based on the following fix: virtee/sev-snp-measure@ae95e59 Signed-off-by: Jagannathan Raman <[email protected]>
New OVMF changes added section SVSM_CAA to OvmfSevMetadata. To calculate the measurement with this new section, the new section has to be added and needs to be treated as zero pages when encountered. Based on the this commit: virtee/sev-snp-measure@cc93bb0 Signed-off-by: Jagannathan Raman <[email protected]>
Signed-off-by: Jagannathan Raman <[email protected]>
@derpsteb Hi Otto, could you please take a look at this PR? Thank you so much! |
@derpsteb Did you get a chance to take a look at this? I'm unable to add you as a reviewer to this PR. Thank you! |
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.
lgtm
@DGonzalezVillal Thanks for approving the PR! Appreciate it. Could you please merge it? I don't have the permissions to do it. Thank you! |
@DGonzalezVillal Could you please merge this? |
My apologies I forgot to merge that one time |
No description provided.