aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/virtual/kvm/api.txt
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/virtual/kvm/api.txt')
-rw-r--r--Documentation/virtual/kvm/api.txt15
1 files changed, 15 insertions, 0 deletions
diff --git a/Documentation/virtual/kvm/api.txt b/Documentation/virtual/kvm/api.txt
index 556d056a9bcd..6a5de5643e0b 100644
--- a/Documentation/virtual/kvm/api.txt
+++ b/Documentation/virtual/kvm/api.txt
@@ -2740,6 +2740,21 @@ It gets triggered whenever both KVM_CAP_PPC_EPR are enabled and an
2740external interrupt has just been delivered into the guest. User space 2740external interrupt has just been delivered into the guest. User space
2741should put the acknowledged interrupt vector into the 'epr' field. 2741should put the acknowledged interrupt vector into the 'epr' field.
2742 2742
2743 /* KVM_EXIT_SYSTEM_EVENT */
2744 struct {
2745#define KVM_SYSTEM_EVENT_SHUTDOWN 1
2746#define KVM_SYSTEM_EVENT_RESET 2
2747 __u32 type;
2748 __u64 flags;
2749 } system_event;
2750
2751If exit_reason is KVM_EXIT_SYSTEM_EVENT then the vcpu has triggered
2752a system-level event using some architecture specific mechanism (hypercall
2753or some special instruction). In case of ARM/ARM64, this is triggered using
2754HVC instruction based PSCI call from the vcpu. The 'type' field describes
2755the system-level event type. The 'flags' field describes architecture
2756specific flags for the system-level event.
2757
2743 /* Fix the size of the union. */ 2758 /* Fix the size of the union. */
2744 char padding[256]; 2759 char padding[256];
2745 }; 2760 };