| Message ID | 20190806165429.19327-2-brijesh.singh@amd.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | Add SEV guest live migration support | expand |
* Singh, Brijesh (brijesh.singh@amd.com) wrote: > Signed-off-by: Brijesh Singh <brijesh.singh@amd.com> > --- > docs/amd-memory-encryption.txt | 8 ++++---- > 1 file changed, 4 insertions(+), 4 deletions(-) > > diff --git a/docs/amd-memory-encryption.txt b/docs/amd-memory-encryption.txt > index 43bf3ee6a5..8822cadda1 100644 > --- a/docs/amd-memory-encryption.txt > +++ b/docs/amd-memory-encryption.txt > @@ -67,8 +67,8 @@ expects. > LAUNCH_FINISH command finalizes the guest launch and destroy's the cryptographic > context. > > -See SEV KM API Spec [1] 'Launching a guest' usage flow (Appendix A) for the > -complete flow chart. > +See Secure Encrypted Virtualization Key Management API spec section > +'Launching a guest' usage flow (Appendix A) for the complete flow chart. > > To launch a SEV guest > > @@ -97,8 +97,8 @@ References > AMD Memory Encryption whitepaper: > http://amd-dev.wpengine.netdna-cdn.com/wordpress/media/2013/12/AMD_Memory_Encryption_Whitepaper_v7-Public.pdf > > -Secure Encrypted Virtualization Key Management: > -[1] http://support.amd.com/TechDocs/55766_SEV-KM API_Specification.pdf > +Secure Encrypted Virtualization Key Management API Spec: > +[1] https://developer.amd.com/sev/ (Secure Encrypted Virtualization API) Yep, that's better; note the document name seems to have lost the words 'key management' at some time; but: Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com> > KVM Forum slides: > http://www.linux-kvm.org/images/7/74/02x08A-Thomas_Lendacky-AMDs_Virtualizatoin_Memory_Encryption_Technology.pdf > -- > 2.17.1 > -- Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
diff --git a/docs/amd-memory-encryption.txt b/docs/amd-memory-encryption.txt index 43bf3ee6a5..8822cadda1 100644 --- a/docs/amd-memory-encryption.txt +++ b/docs/amd-memory-encryption.txt @@ -67,8 +67,8 @@ expects. LAUNCH_FINISH command finalizes the guest launch and destroy's the cryptographic context. -See SEV KM API Spec [1] 'Launching a guest' usage flow (Appendix A) for the -complete flow chart. +See Secure Encrypted Virtualization Key Management API spec section +'Launching a guest' usage flow (Appendix A) for the complete flow chart. To launch a SEV guest @@ -97,8 +97,8 @@ References AMD Memory Encryption whitepaper: http://amd-dev.wpengine.netdna-cdn.com/wordpress/media/2013/12/AMD_Memory_Encryption_Whitepaper_v7-Public.pdf -Secure Encrypted Virtualization Key Management: -[1] http://support.amd.com/TechDocs/55766_SEV-KM API_Specification.pdf +Secure Encrypted Virtualization Key Management API Spec: +[1] https://developer.amd.com/sev/ (Secure Encrypted Virtualization API) KVM Forum slides: http://www.linux-kvm.org/images/7/74/02x08A-Thomas_Lendacky-AMDs_Virtualizatoin_Memory_Encryption_Technology.pdf
Signed-off-by: Brijesh Singh <brijesh.singh@amd.com> --- docs/amd-memory-encryption.txt | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)