From: Tom Lendacky <thomas.lendacky@amd.com>
To: Melody Wang <huibo.wang@amd.com>,
Sean Christopherson <seanjc@google.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, KVM <kvm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Dhaval Giani <dhaval.giani@amd.com>
Subject: Re: [PATCH v4 0/2] KVM: SVM: Make VMGEXIT GHCB exit codes more readable
Date: Thu, 2 Jan 2025 08:58:01 -0600 [thread overview]
Message-ID: <84f5e0b9-655a-9503-1781-26c31cb062eb@amd.com> (raw)
In-Reply-To: <cover.1735590556.git.huibo.wang@amd.com>
On 12/30/24 14:36, Melody Wang wrote:
Just some FYIs when it comes to cover letters.
> Hi all,
No need to put this in a cover letter.
>
> This patchset addresses all of review comments from Sean. All feedback is appreciated.
This should be part of your change log below.
Here you should have a summary of what the series is about.
>
> Thanks,
> Melody
>
> Changelog:
> v3:
You're missing the changes from v3 to v4 and you shouldn't delete the
previous log of changes from v1 to v2 and v2 to v3.
>
> Here are two patches to make VMGEXIT GHCB exit codes more readable. All
> feedback is appreciated.
This should be at the top. Also, this isn't for exit codes, it is for the
hypervisor return error codes, right?
Thanks,
Tom
>
> Melody Wang (2):
> KVM: SVM: Convert plain error code numbers to defines
> KVM: SVM: Provide helpers to set the error code
>
> arch/x86/include/asm/sev-common.h | 8 +++++++
> arch/x86/kvm/svm/sev.c | 36 ++++++++++++++++---------------
> arch/x86/kvm/svm/svm.c | 6 +-----
> arch/x86/kvm/svm/svm.h | 29 +++++++++++++++++++++++++
> 4 files changed, 57 insertions(+), 22 deletions(-)
>
prev parent reply other threads:[~2025-01-02 14:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-30 20:36 Melody Wang
2024-12-30 20:36 ` [PATCH v4 1/2] KVM: SVM: Convert plain error code numbers to defines Melody Wang
2024-12-30 20:36 ` [PATCH v4 2/2] KVM: SVM: Provide helpers to set the error code Melody Wang
2025-01-02 14:09 ` Paluri, PavanKumar
2025-01-02 14:58 ` Tom Lendacky [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=84f5e0b9-655a-9503-1781-26c31cb062eb@amd.com \
--to=thomas.lendacky@amd.com \
--cc=dhaval.giani@amd.com \
--cc=huibo.wang@amd.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
/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®