-
Notifications
You must be signed in to change notification settings - Fork 84
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
tee: Remove legacy AMD-SEV module #271
Conversation
The clippy warnings are handled by #272. Once that is merged, this can be rebased. |
To prepare for the updating of the Rust SEV library to 5.0.0, remove the legacy SEV/SEV-ES module. AMD has all but deprecated legacy SEV, and has instead opted to push all new development to SEV-SNP. As such, the SEV library is intending to deprecate legacy SEV. Signed-off-by: Tyler Fanelli <[email protected]>
bf6f9b6
to
8e8df98
Compare
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.
Do you plan on removing the SEV-related code in init/ as well?
Other than that, LGTM. Just a non-blocking question below.
sev: Option<AmdSev>, | ||
tee: Option<AmdSnp>, |
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.
Not blocking, but I'm wondering if this should be named snp: ...
? It's going to get re-named once TDX and CCA land anyways
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.
Yea, will rename.
That is all SEV-SNP specific. |
It's kind of sad to see this go, but I guess it's for the better. |
To prepare for the updating of the Rust SEV library to 5.0.0, remove the legacy SEV/SEV-ES module. AMD has all but deprecated legacy SEV, and has instead opted to push all new development to SEV-SNP.
As such, the SEV library is intending to deprecate legacy SEV.