From: Sean Christopherson <seanjc@google.com>
To: Melody Wang <huibo.wang@amd.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, KVM <kvm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Tom Lendacky <thomas.lendacky@amd.com>,
Dhaval Giani <dhaval.giani@amd.com>
Subject: Re: [PATCH 0/2] KVM: SVM: Make VMGEXIT GHCB exit codes more readable
Date: Mon, 16 Dec 2024 16:29:33 -0800 [thread overview]
Message-ID: <Z2DF7UFNt1vayroN@google.com> (raw)
In-Reply-To: <20241206221257.7167-1-huibo.wang@amd.com>
On Fri, Dec 06, 2024, Melody Wang wrote:
> Hi all,
>
> Here are two patches to make VMGEXIT GHCB exit codes more readable. All
> feedback is appreciated.
>
> Thanks,
> Melody
>
> Melody Wang (2):
> KVM: SVM: Convert plain error code numbers to defines
When adding patches to a series, please treat the "new" series as a continuation
of the previous series, and follow all of the normal "rules" for documenting the
delta between versions. I.e. this should be v3, since patch 1 was posted as v2.
https://lore.kernel.org/all/20241202214032.350109-1-huibo.wang@amd.com
> KVM: SVM: Provide helpers to set the error code
>
> arch/x86/include/asm/sev-common.h | 8 +++++++
> arch/x86/kvm/svm/sev.c | 39 +++++++++++++++++--------------
> arch/x86/kvm/svm/svm.c | 6 +----
> arch/x86/kvm/svm/svm.h | 24 +++++++++++++++++++
> 4 files changed, 54 insertions(+), 23 deletions(-)
>
> --
> 2.34.1
>
prev parent reply other threads:[~2024-12-17 0:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 22:12 [PATCH 0/2] KVM: SVM: Make VMGEXIT GHCB exit codes more readable Melody Wang
2024-12-06 22:12 ` [PATCH 1/2] KVM: SVM: Convert plain error code numbers to defines Melody Wang
2024-12-17 0:41 ` Sean Christopherson
2024-12-17 16:03 ` Paluri, PavanKumar
2024-12-17 22:43 ` Sean Christopherson
2024-12-06 22:12 ` [PATCH 2/2] KVM: SVM: Provide helpers to set the error code Melody Wang
2024-12-17 0:56 ` Sean Christopherson
2024-12-17 0:29 ` Sean Christopherson [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=Z2DF7UFNt1vayroN@google.com \
--to=seanjc@google.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=thomas.lendacky@amd.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