All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: PavanKumar Paluri <papaluri@amd.com>
Cc: Melody Wang <huibo.wang@amd.com>,
	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>,
	Pavan Kumar <pavankumar.paluri@amd.com>
Subject: Re: [PATCH 1/2] KVM: SVM: Convert plain error code numbers to defines
Date: Tue, 17 Dec 2024 14:43:29 -0800	[thread overview]
Message-ID: <Z2H-Y5eskBqeYo9Z@google.com> (raw)
In-Reply-To: <bbda7d0d-48c0-4c05-a107-85a30b5c2987@amd.com>

On Tue, Dec 17, 2024, PavanKumar Paluri wrote:
> >> +#define GHCB_HV_RESP_ISSUE_EXCEPTION	1
> >> +#define GHCB_HV_RESP_MALFORMED_INPUT	2
> > 
> > Where is '2' actually documented?  I looked all over the GHCB and the only ones
> > I can find are '0' and '1'.
> > 
> >   0x0000
> >     o No action requested by the hypervisor.
> >   0x0001
> >     o The hypervisor has requested an exception be issued
> > 
> 
> GHCB spec (Pub# 56421, Rev:2.03), section 4.1 Invoking VMGEXIT documents

Ah, I only had Rev 2.00.  Found it in 2.03.

Thanks!

> 0x0002 as well.
> 
> 0x0002
>  o The hypervisor encountered malformed input for the VMGEXIT.

  reply	other threads:[~2024-12-17 22:43 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 [this message]
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 ` [PATCH 0/2] KVM: SVM: Make VMGEXIT GHCB exit codes more readable Sean Christopherson

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=Z2H-Y5eskBqeYo9Z@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=papaluri@amd.com \
    --cc=pavankumar.paluri@amd.com \
    --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 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.