Re: [PATCH 0/5] Provide SEV-ES/SEV-SNP support for decrypting the VMSA

[Tom Lendacky <thomas.lendacky@amd.com>]

On 4/25/25 18:23, Sean Christopherson wrote:
> On Thu, 20 Mar 2025 08:26:48 -0500, Tom Lendacky wrote:
>> This series adds support for decrypting an SEV-ES/SEV-SNP VMSA in
>> dump_vmcb() when the guest policy allows debugging.
>>
>> It also contains some updates to dump_vmcb() to dump additional guest
>> register state, print the type of guest, print the vCPU id, and adds a
>> mutex to prevent interleaving of the dump_vmcb() messages when multiple
>> vCPU threads call dump_vmcb(). These last patches can be dropped if not
>> desired.
>>
>> [...]
> 
> Applied to kvm-x86 svm, with Tom's fixups.  Please double check I didn't botch
> those, the last few days have been a never ending comedy of errors on my end.

Everything looks good.

Thanks!
Tom

> 
> Thanks!
> 
> [1/5] KVM: SVM: Decrypt SEV VMSA in dump_vmcb() if debugging is enabled
>       https://github.com/kvm-x86/linux/commit/962e2b6152ef
> [2/5] KVM: SVM: Dump guest register state in dump_vmcb()
>       https://github.com/kvm-x86/linux/commit/22f5c2003a18
> [3/5] KVM: SVM: Add the type of VM for which the VMCB/VMSA is being dumped
>       https://github.com/kvm-x86/linux/commit/db2645096105
> [4/5] KVM: SVM: Include the vCPU ID when dumping a VMCB
>       https://github.com/kvm-x86/linux/commit/0e6b677de730
> [5/5] KVM: SVM: Add a mutex to dump_vmcb() to prevent concurrent output
>       https://github.com/kvm-x86/linux/commit/468c27ae0215
> 
> --
> https://github.com/kvm-x86/linux/tree/next