| commit | ec010c00665ba1e78e6b3df104f923c4ea68504a | |
| author | Nicholas Piggin <npiggin@gmail.com> | |
| Wed, 25 Mar 2020 14:29:03 +0000 (26 00:29 +1000) | ||
| committer | David Gibson <david@gibson.dropbear.id.au> | |
| Mon, 6 Apr 2020 22:55:10 +0000 (7 08:55 +1000) | ||
| tree | fd21867008d11d44d80364a2bf6359049d3a7e47 | treesnapshot (tar.gz zip) |
| parent | 79178edd2a0b012c5cd27e0168beb83ef4b617ef | commitdiff |
ppc/spapr: KVM FWNMI should not be enabled until guest requests it
The KVM FWNMI capability should be enabled with the "ibm,nmi-register"
rtas call. Although MCEs from KVM will be delivered as architected
interrupts to the guest before "ibm,nmi-register" is called, KVM has
different behaviour depending on whether the guest has enabled FWNMI
(it attempts to do more recovery on behalf of a non-FWNMI guest).
Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
Message-Id: <20200325142906.221248-2-npiggin@gmail.com>
Reviewed-by: Greg Kurz <groug@kaod.org>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
The KVM FWNMI capability should be enabled with the "ibm,nmi-register"
rtas call. Although MCEs from KVM will be delivered as architected
interrupts to the guest before "ibm,nmi-register" is called, KVM has
different behaviour depending on whether the guest has enabled FWNMI
(it attempts to do more recovery on behalf of a non-FWNMI guest).
Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
Message-Id: <20200325142906.221248-2-npiggin@gmail.com>
Reviewed-by: Greg Kurz <groug@kaod.org>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
| hw/ppc/spapr_caps.c | diffblobblamehistory | |
| hw/ppc/spapr_rtas.c | diffblobblamehistory | |
| target/ppc/kvm.c | diffblobblamehistory | |
| target/ppc/kvm_ppc.h | diffblobblamehistory |