From: Kim Phillips <kim.phillips@amd.com>
To: Borislav Petkov <bp@alien8.de>, Tom Lendacky <thomas.lendacky@amd.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
x86@kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
Sean Christopherson <seanjc@google.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Michael Roth <michael.roth@amd.com>
Subject: Re: [PATCH 0/5] Provide SEV-ES/SEV-SNP support for decrypting the VMSA
Date: Fri, 21 Mar 2025 13:43:51 -0500 [thread overview]
Message-ID: <e5d67d43-49c9-4c85-97fe-d8a8c61b0174@amd.com> (raw)
In-Reply-To: <20250320141707.GBZ9wjY42cY7_dQ4ql@fat_crate.local>
On 3/20/25 9:17 AM, Borislav Petkov wrote:
> On Thu, Mar 20, 2025 at 08:26:48AM -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.
>
> I would really really love to have that so
>
> Acked-by: Borislav Petkov (AMD) <bp@alien8.de>
Me too.
Tested-by: Kim Phillips <kim.phillips@amd.com>
Thanks,
Kim
kvm_amd: SEV-SNP vCPU1 VMCB 00000000759a48a5, last attempted VMRUN on CPU 7
kvm_amd: VMCB Control Area:
kvm_amd: cr_read: 0000
kvm_amd: cr_write: 0000
kvm_amd: dr_read: 0080
kvm_amd: dr_write: 0080
kvm_amd: exceptions: 00060002
kvm_amd: intercepts: bccc8007 0111ce43
kvm_amd: pause filter count: 3000
kvm_amd: pause filter threshold:128
kvm_amd: iopm_base_pa: 0000000148e44000
kvm_amd: msrpm_base_pa: 0000000276e3e000
kvm_amd: tsc_offset: ffff6b01ea8aa6f6
kvm_amd: asid: 3
kvm_amd: tlb_ctl: 0
kvm_amd: int_ctl: 07000200
kvm_amd: int_vector: 00000000
kvm_amd: int_state: 00000000
kvm_amd: exit_code: ffffffff
kvm_amd: exit_info1: 0000000000000000
kvm_amd: exit_info2: 0000000000000000
kvm_amd: exit_int_info: 00000000
kvm_amd: exit_int_info_err: 00000000
kvm_amd: nested_ctl: 7
kvm_amd: nested_cr3: 000000022fc06000
kvm_amd: avic_vapic_bar: 0000000000000000
kvm_amd: ghcb: 00000000bfeda000
kvm_amd: event_inj: 00000000
kvm_amd: event_inj_err: 00000000
kvm_amd: virt_ext: 3
kvm_amd: next_rip: 0000000000000000
kvm_amd: avic_backing_page: 0000000000000000
kvm_amd: avic_logical_id: 0000000000000000
kvm_amd: avic_physical_id: 0000000000000000
kvm_amd: vmsa_pa: 00000005d35c0000
kvm_amd: allowed_sev_features:8000000000000001
kvm_amd: guest_sev_features: 0000000000000081
kvm_amd: VMCB State Save Area:
kvm_amd: es: s: 0000 a: 0092 l: 0000ffff b: 0000000000000000
kvm_amd: cs: s: 9900 a: 009a l: 0000ffff b: 0000000000099000
kvm_amd: ss: s: 0000 a: 0092 l: 0000ffff b: 0000000000000000
kvm_amd: ds: s: 0000 a: 0092 l: 0000ffff b: 0000000000000000
kvm_amd: fs: s: 0000 a: 0092 l: 0000ffff b: 0000000000000000
kvm_amd: gs: s: 0000 a: 0092 l: 0000ffff b: 0000000000000000
kvm_amd: gdtr: s: 0000 a: 0000 l: 0000ffff b: 0000000000000000
kvm_amd: ldtr: s: 0000 a: 0082 l: 0000ffff b: 0000000000000000
kvm_amd: idtr: s: 0000 a: 0000 l: 0000ffff b: 0000000000000000
kvm_amd: tr: s: 0000 a: 0083 l: 0000ffff b: 0000000000000000
kvm_amd: vmpl: 0 cpl: 0 efer: 0000000000001000
kvm_amd: cr0: 0000000060000010 cr2: 0000000000000000
kvm_amd: cr3: 0000000000000000 cr4: 0000000000000040
kvm_amd: dr6: 00000000ffff0ff0 dr7: 0000000000000400
kvm_amd: rip: 0000000000000050 rflags: 0000000000000002
kvm_amd: rsp: 0000000000000000 rax: 0000000000000000
kvm_amd: star: 0000000000000000 lstar: 0000000000000000
kvm_amd: cstar: 0000000000000000 sfmask: 0000000000000000
kvm_amd: kernel_gs_base: 0000000000000000 sysenter_cs: 0000000000000000
kvm_amd: sysenter_esp: 0000000000000000 sysenter_eip: 0000000000000000
kvm_amd: gpat: 0007040600070406 dbgctl: 0000000000000000
kvm_amd: br_from: 0000000000000000 br_to: 0000000000000000
kvm_amd: excp_from: 0000000000000000 excp_to: 0000000000000000
kvm_amd: sev_features 0000000000000081
kvm_amd: rax: 0000000000000000 rbx: 0000000000000000
kvm_amd: rcx: 0000000000000000 rdx: 0000000000000000
kvm_amd: rsi: 0000000000000000 rdi: 0000000000000000
kvm_amd: rbp: 0000000000000000 rsp: 0000000000000000
kvm_amd: r8: 0000000000000000 r9: 0000000000000000
kvm_amd: r10: 0000000000000000 r11: 0000000000000000
kvm_amd: r12: 0000000000000000 r13: 0000000000000000
kvm_amd: r14: 0000000000000000 r15: 0000000000000000
kvm_amd: xcr0: 0000000000000001 xss: 0000000000000000
next prev parent reply other threads:[~2025-03-21 18:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 13:26 Tom Lendacky
2025-03-20 13:26 ` [PATCH 1/5] KVM: SVM: Decrypt SEV VMSA in dump_vmcb() if debugging is enabled Tom Lendacky
2025-03-21 14:36 ` Tom Lendacky
2025-03-21 14:40 ` Tom Lendacky
2025-03-24 21:31 ` Tom Lendacky
2025-04-10 23:14 ` Sean Christopherson
2025-04-14 16:11 ` Tom Lendacky
2025-04-14 17:20 ` Tom Lendacky
2025-03-20 13:26 ` [PATCH 2/5] KVM: SVM: Dump guest register state in dump_vmcb() Tom Lendacky
2025-03-20 13:26 ` [PATCH 3/5] KVM: SVM: Add the type of VM for which the VMCB/VMSA is being dumped Tom Lendacky
2025-03-20 13:26 ` [PATCH 4/5] KVM: SVM: Include the vCPU ID when dumping a VMCB Tom Lendacky
2025-03-20 13:26 ` [PATCH 5/5] KVM: SVM: Add a mutex to dump_vmcb() to prevent concurrent output Tom Lendacky
2025-03-20 14:17 ` [PATCH 0/5] Provide SEV-ES/SEV-SNP support for decrypting the VMSA Borislav Petkov
2025-03-21 18:43 ` Kim Phillips [this message]
2025-04-25 23:23 ` Sean Christopherson
2025-04-26 14:53 ` Tom Lendacky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e5d67d43-49c9-4c85-97fe-d8a8c61b0174@amd.com \
--to=kim.phillips@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.roth@amd.com \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®