All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Sean Christopherson <seanjc@google.com>,
	Vitaly Kuznetsov <vkuznets@redhat.com>,
	Wanpeng Li <wanpengli@tencent.com>,
	Jim Mattson <jmattson@google.com>,
	x86@kernel.org, Brijesh Singh <brijesh.singh@amd.com>,
	Tom Lendacky <thomas.lendacky@amd.com>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Joerg Roedel <jroedel@suse.de>
Subject: Re: [PATCH v6 0/7] KVM: SVM: Add initial GHCB protocol version 2 support
Date: Fri, 25 Feb 2022 11:40:44 +0100	[thread overview]
Message-ID: <YhiyLJOHyfA7sLMt@8bytes.org> (raw)
In-Reply-To: <20220125141626.16008-1-joro@8bytes.org>

Gentle ping. Any comments on these patches?

On Tue, Jan 25, 2022 at 03:16:19PM +0100, Joerg Roedel wrote:
> From: Joerg Roedel <jroedel@suse.de>
> 
> Hi,
> 
> here is a small set of patches which I originally took from the
> pending SEV-SNP patch-sets to enable basic support for GHCB protocol
> version 2. Meanwhile a couple of other patches from Sean
> Christopherson have been added.
> 
> When SEV-SNP is not supported, only two new MSR protocol VMGEXIT calls
> are required:
> 
> 	- MSR-based AP-reset-hold
> 	- MSR-based HV-feature-request
> 
> These calls are implemented here and then the protocol is lifted to
> version 2.
> 
> This is submitted separately because the MSR-based AP-reset-hold call
> is required to support kexec/kdump in SEV-ES guests.
> 
> The previous version can be found here:
> 
> 	https://lore.kernel.org/kvm/20211020124416.24523-1-joro@8bytes.org/
> 
> Regards,
> 
> 	Joerg
> 
> Changes v5->v6:
> 
> 	- Rebased to v5.17-rc1
> 	- Added changes requested by Sean Christopherson
> 
> Brijesh Singh (2):
>   KVM: SVM: Add support for Hypervisor Feature support MSR protocol
>   KVM: SVM: Increase supported GHCB protocol version
> 
> Joerg Roedel (2):
>   KVM: SVM: Get rid of set_ghcb_msr() and *ghcb_msr_bits() functions
>   KVM: SVM: Move kvm_emulate_ap_reset_hold() to AMD specific code
> 
> Sean Christopherson (2):
>   KVM: SVM: Add helper to generate GHCB MSR verson info, and drop macro
>   KVM: SVM: Set "released" on INIT-SIPI iff SEV-ES vCPU was in AP reset
>     hold
> 
> Tom Lendacky (1):
>   KVM: SVM: Add support to handle AP reset MSR protocol
> 
>  arch/x86/include/asm/kvm_host.h   |   2 +-
>  arch/x86/include/asm/sev-common.h |  18 ++--
>  arch/x86/include/uapi/asm/svm.h   |   1 +
>  arch/x86/kvm/svm/sev.c            | 169 ++++++++++++++++++++----------
>  arch/x86/kvm/svm/svm.c            |  13 ++-
>  arch/x86/kvm/svm/svm.h            |  10 +-
>  arch/x86/kvm/x86.c                |  12 +--
>  7 files changed, 137 insertions(+), 88 deletions(-)
> 
> 
> base-commit: e783362eb54cd99b2cac8b3a9aeac942e6f6ac07
> -- 
> 2.34.1

      parent reply	other threads:[~2022-02-25 10:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-25 14:16 [PATCH v6 0/7] KVM: SVM: Add initial GHCB protocol version 2 support Joerg Roedel
2022-01-25 14:16 ` [PATCH v6 1/7] KVM: SVM: Get rid of set_ghcb_msr() and *ghcb_msr_bits() functions Joerg Roedel
2022-01-25 14:16 ` [PATCH v6 2/7] KVM: SVM: Add helper to generate GHCB MSR verson info, and drop macro Joerg Roedel
2022-01-25 14:16 ` [PATCH v6 3/7] KVM: SVM: Move kvm_emulate_ap_reset_hold() to AMD specific code Joerg Roedel
2022-01-25 14:16 ` [PATCH v6 4/7] KVM: SVM: Set "released" on INIT-SIPI iff SEV-ES vCPU was in AP reset hold Joerg Roedel
2022-01-25 14:16 ` [PATCH v6 5/7] KVM: SVM: Add support to handle AP reset MSR protocol Joerg Roedel
2022-01-25 14:16 ` [PATCH v6 6/7] KVM: SVM: Add support for Hypervisor Feature support " Joerg Roedel
2022-01-25 14:16 ` [PATCH v6 7/7] KVM: SVM: Increase supported GHCB protocol version Joerg Roedel
2022-02-25 10:40 ` Joerg Roedel [this message]

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=YhiyLJOHyfA7sLMt@8bytes.org \
    --to=joro@8bytes.org \
    --cc=brijesh.singh@amd.com \
    --cc=jmattson@google.com \
    --cc=jroedel@suse.de \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.com \
    --cc=thomas.lendacky@amd.com \
    --cc=vkuznets@redhat.com \
    --cc=wanpengli@tencent.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.