From: Nicholas Piggin <npiggin@gmail.com>
To: qemu-ppc@nongnu.org
Cc: "Aravinda Prasad" <arawinda.p@gmail.com>,
"Alexey Kardashevskiy" <aik@ozlabs.ru>,
qemu-devel@nongnu.org, "Nicholas Piggin" <npiggin@gmail.com>,
"Greg Kurz" <groug@kaod.org>, "Cédric Le Goater" <clg@fr.ibm.com>,
"Ganesh Goudar" <ganeshgr@linux.ibm.com>,
"David Gibson" <david@gibson.dropbear.id.au>
Subject: [PATCH 4/5] ppc/spapr: Don't kill the guest if a recovered FWNMI machine check delivery fails
Date: Tue, 17 Mar 2020 15:02:14 +1000 [thread overview]
Message-ID: <20200317050215.159334-5-npiggin@gmail.com> (raw)
In-Reply-To: <20200317050215.159334-1-npiggin@gmail.com>
Try to be tolerant of errors if the machine check had been recovered
by the host.
Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
---
hw/ppc/spapr_events.c | 25 ++++++++++++++++++-------
1 file changed, 18 insertions(+), 7 deletions(-)
diff --git a/hw/ppc/spapr_events.c b/hw/ppc/spapr_events.c
index d35151eeb0..3f524cb0ca 100644
--- a/hw/ppc/spapr_events.c
+++ b/hw/ppc/spapr_events.c
@@ -807,13 +807,20 @@ static void spapr_mce_dispatch_elog(PowerPCCPU *cpu, bool recovered)
/* get rtas addr from fdt */
rtas_addr = spapr_get_rtas_addr();
if (!rtas_addr) {
- warn_report("FWNMI: Unable to deliver machine check to guest: "
- "rtas_addr not found.");
- qemu_system_guest_panicked(NULL);
+ if (!recovered) {
+ warn_report("FWNMI: Unable to deliver machine check to guest: "
+ "rtas_addr not found.");
+ qemu_system_guest_panicked(NULL);
+ } else {
+ warn_report("FWNMI: Unable to deliver machine check to guest: "
+ "rtas_addr not found. Machine check recovered.");
+ }
g_free(ext_elog);
return;
}
+ spapr->fwnmi_machine_check_interlock = cpu->vcpu_id;
+
stq_be_phys(&address_space_memory, rtas_addr + RTAS_ERROR_LOG_OFFSET,
env->gpr[3]);
cpu_physical_memory_write(rtas_addr + RTAS_ERROR_LOG_OFFSET +
@@ -850,9 +857,14 @@ void spapr_mce_req_event(PowerPCCPU *cpu, bool recovered)
* that CPU called "ibm,nmi-interlock")
*/
if (spapr->fwnmi_machine_check_interlock == cpu->vcpu_id) {
- warn_report("FWNMI: Unable to deliver machine check to guest: "
- "nested machine check.");
- qemu_system_guest_panicked(NULL);
+ if (!recovered) {
+ warn_report("FWNMI: Unable to deliver machine check to guest: "
+ "nested machine check.");
+ qemu_system_guest_panicked(NULL);
+ } else {
+ warn_report("FWNMI: Unable to deliver machine check to guest: "
+ "nested machine check. Machine check recovered.");
+ }
return;
}
qemu_cond_wait_iothread(&spapr->fwnmi_machine_check_interlock_cond);
@@ -880,7 +892,6 @@ void spapr_mce_req_event(PowerPCCPU *cpu, bool recovered)
warn_report("Received a fwnmi while migration was in progress");
}
- spapr->fwnmi_machine_check_interlock = cpu->vcpu_id;
spapr_mce_dispatch_elog(cpu, recovered);
}
--
2.23.0
next prev parent reply other threads:[~2020-03-17 5:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-17 5:02 [PATCH 0/5] FWNMI follow up patches Nicholas Piggin
2020-03-17 5:02 ` [PATCH 1/5] ppc/spapr: KVM FWNMI should not be enabled until guest requests it Nicholas Piggin
2020-03-17 11:02 ` Greg Kurz
2020-03-19 2:27 ` Nicholas Piggin
2020-03-17 5:02 ` [PATCH 2/5] ppc/spapr: Improve FWNMI machine check delivery corner case comments Nicholas Piggin
2020-03-17 12:16 ` Greg Kurz
2020-03-17 5:02 ` [PATCH 3/5] ppc/spapr: Add FWNMI machine check delivery warnings Nicholas Piggin
2020-03-17 12:20 ` Greg Kurz
2020-03-19 2:28 ` Nicholas Piggin
2020-03-17 5:02 ` Nicholas Piggin [this message]
2020-03-17 16:57 ` [PATCH 4/5] ppc/spapr: Don't kill the guest if a recovered FWNMI machine check delivery fails Greg Kurz
2020-03-19 2:29 ` Nicholas Piggin
2020-03-17 5:02 ` [PATCH 5/5] target/ppc: Implement simple monitor mce injection Nicholas Piggin
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=20200317050215.159334-5-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=aik@ozlabs.ru \
--cc=arawinda.p@gmail.com \
--cc=clg@fr.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=ganeshgr@linux.ibm.com \
--cc=groug@kaod.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).