From: Joerg Roedel <jroedel@suse.de>
To: Sean Christopherson <seanjc@google.com>
Cc: Joerg Roedel <joro@8bytes.org>,
Paolo Bonzini <pbonzini@redhat.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
Subject: Re: [PATCH v4 3/5] KVM: SVM: Add support to handle AP reset MSR protocol
Date: Wed, 20 Oct 2021 14:32:11 +0200 [thread overview]
Message-ID: <YXAMSyr3uByu4byY@suse.de> (raw)
In-Reply-To: <YWdX1WXE3AOPFC6d@google.com>
On Wed, Oct 13, 2021 at 10:04:05PM +0000, Sean Christopherson wrote:
> Rather than put more stuff into x86 that really belongs to SEV, what about moving
> kvm_emulate_ap_reset_hold() into sev.c and instead exporting __kvm_vcpu_halt()?
Did that in a separate patch and fixed things up. Also replaced the kvm_
with and sev_ prefix and the function now takes an vcpu_svm parameter.
New version coming soon.
Thanks,
Joerg
next prev parent reply other threads:[~2021-10-20 12:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 15:53 [PATCH v4 0/5] KVM: SVM: Add initial GHCB protocol version 2 support Joerg Roedel
2021-09-29 15:53 ` [PATCH v4 1/5] KVM: SVM: Get rid of set_ghcb_msr() and *ghcb_msr_bits() functions Joerg Roedel
2021-10-13 22:07 ` Sean Christopherson
2021-09-29 15:53 ` [PATCH v4 2/5] KVM: SVM: Add helper to generate GHCB MSR version info, and drop macro Joerg Roedel
2021-09-29 15:53 ` [PATCH v4 3/5] KVM: SVM: Add support to handle AP reset MSR protocol Joerg Roedel
2021-10-13 22:04 ` Sean Christopherson
2021-10-20 12:32 ` Joerg Roedel [this message]
2021-09-29 15:53 ` [PATCH v4 4/5] KVM: SVM: Add support for Hypervisor Feature support " Joerg Roedel
2021-09-29 15:53 ` [PATCH v4 5/5] KVM: SVM: Increase supported GHCB protocol version Joerg Roedel
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=YXAMSyr3uByu4byY@suse.de \
--to=jroedel@suse.de \
--cc=brijesh.singh@amd.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--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.