From: Binbin Wu <binbin.wu@linux.intel.com>
To: Xiaoyao Li <xiaoyao.li@intel.com>,
pbonzini@redhat.com, seanjc@google.com, kvm@vger.kernel.org
Cc: rick.p.edgecombe@intel.com, kai.huang@intel.com,
adrian.hunter@intel.com, reinette.chatre@intel.com,
tony.lindgren@intel.com, isaku.yamahata@intel.com,
yan.y.zhao@intel.com, chao.gao@intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 7/9] KVM: TDX: Handle TDG.VP.VMCALL<ReportFatalError>
Date: Wed, 26 Feb 2025 18:15:00 +0800 [thread overview]
Message-ID: <f16d1df0-0948-4ac4-8487-df790c1773f3@linux.intel.com> (raw)
In-Reply-To: <68f771b1-0a7e-44e7-8db6-956b8cfb4112@intel.com>
On 2/26/2025 5:36 PM, Xiaoyao Li wrote:
> On 2/22/2025 9:42 AM, Binbin Wu wrote:
>> @@ -6849,9 +6850,11 @@ Valid values for 'type' are:
>> reset/shutdown of the VM.
>> - KVM_SYSTEM_EVENT_SEV_TERM -- an AMD SEV guest requested termination.
>> The guest physical address of the guest's GHCB is stored in `data[0]`.
>> - - KVM_SYSTEM_EVENT_WAKEUP -- the exiting vCPU is in a suspended state and
>> - KVM has recognized a wakeup event. Userspace may honor this event by
>> - marking the exiting vCPU as runnable, or deny it and call KVM_RUN again.
>
> It deletes the description of KVM_SYSTEM_EVENT_WAKEUP by mistake;
Oops, sorry for not being careful enough.
>
> (Maybe we can fix the order of the descriptions by the way, KVM_SYSTEM_EVENT_SEV_TERM gets put in front of KVM_SYSTEM_EVENT_WAKEUP and KVM_SYSTEM_EVENT_SUSPEND)
>
>> + - KVM_SYSTEM_EVENT_TDX_FATAL -- a TDX guest reported a fatal error state.
>> + KVM doesn't do any parsing or conversion, it just dumps 16 general-purpose
>> + registers to userspace, in ascending order of the 4-bit indices for x86-64
>> + general-purpose registers in instruction encoding, as defined in the Intel
>> + SDM.
>> - KVM_SYSTEM_EVENT_SUSPEND -- the guest has requested a suspension of
>> the VM.
>
next prev parent reply other threads:[~2025-02-26 10:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-22 1:42 [PATCH v3 0/9] KVM: TDX: TDX hypercalls may exit to userspace Binbin Wu
2025-02-22 1:42 ` [PATCH v3 1/9] KVM: x86: Have ____kvm_emulate_hypercall() read the GPRs Binbin Wu
2025-02-22 1:42 ` [PATCH v3 2/9] KVM: x86: Move pv_unhaulted check out of kvm_vcpu_has_events() Binbin Wu
2025-02-22 1:42 ` [PATCH v3 3/9] KVM: TDX: Add a place holder to handle TDX VM exit Binbin Wu
2025-02-22 1:42 ` [PATCH v3 4/9] KVM: TDX: Add a place holder for handler of TDX hypercalls (TDG.VP.VMCALL) Binbin Wu
2025-02-22 1:42 ` [PATCH v3 5/9] KVM: TDX: Handle KVM hypercall with TDG.VP.VMCALL Binbin Wu
2025-02-22 1:42 ` [PATCH v3 6/9] KVM: TDX: Handle TDG.VP.VMCALL<MapGPA> Binbin Wu
2025-02-22 1:42 ` [PATCH v3 7/9] KVM: TDX: Handle TDG.VP.VMCALL<ReportFatalError> Binbin Wu
2025-02-26 9:36 ` Xiaoyao Li
2025-02-26 10:15 ` Binbin Wu [this message]
2025-02-22 1:42 ` [PATCH v3 8/9] KVM: TDX: Handle TDX PV port I/O hypercall Binbin Wu
2025-02-22 1:42 ` [PATCH v3 9/9] KVM: TDX: Handle TDX PV MMIO hypercall Binbin Wu
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=f16d1df0-0948-4ac4-8487-df790c1773f3@linux.intel.com \
--to=binbin.wu@linux.intel.com \
--cc=adrian.hunter@intel.com \
--cc=chao.gao@intel.com \
--cc=isaku.yamahata@intel.com \
--cc=kai.huang@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=reinette.chatre@intel.com \
--cc=rick.p.edgecombe@intel.com \
--cc=seanjc@google.com \
--cc=tony.lindgren@intel.com \
--cc=xiaoyao.li@intel.com \
--cc=yan.y.zhao@intel.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