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.
