From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Nicholas Piggin <npiggin@gmail.com>, qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org,
"Daniel Henrique Barboza" <danielhb413@gmail.com>,
"Cédric Le Goater" <clg@kaod.org>,
"David Gibson" <david@gibson.dropbear.id.au>,
"Greg Kurz" <groug@kaod.org>,
"Harsh Prateek Bora" <harshpb@linux.ibm.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"BALATON Zoltan" <balaton@eik.bme.hu>
Subject: Re: [PATCH v3] target/ppc: Make checkstop actually stop the system
Date: Mon, 3 Jul 2023 15:26:52 +0200 [thread overview]
Message-ID: <9fbf9403-fbfe-4d84-7ca4-aae19e9d207e@linaro.org> (raw)
In-Reply-To: <20230703120340.45349-1-npiggin@gmail.com>
On 3/7/23 14:03, Nicholas Piggin wrote:
> checkstop state does not halt the system, interrupts continue to be
> serviced, and other CPUs run. Stop the machine with
> qemu_system_guest_panicked.
>
> Change the logging not to print separately to stderr because a
> checkstop is a guest error (or perhaps a simulated machine error)
> rather than a QEMU error. CPU registers are dumped.
>
> Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
<here ...>
>
> Since v1:
> - Fix loop exit so it stops on the checkstop-causing instruction, rather than
> after it.
>
> Since v2:
> - Rebase on ppc-next.
[*]
> - Use qemu_system_guest_panicked rather than vm_stop (Richard)
> - Move away from printing to stderr (Zoltan)
> - Reduce changes to log messages.
> - Split out from larger series since it's independent (will skip attn
> instruction for now).
> ---
... goes this line, so the version changes are stripped out
when the patch is applied (usually they are not useful in the
git history).
> target/ppc/excp_helper.c | 26 ++++++++++++++++++--------
> 1 file changed, 18 insertions(+), 8 deletions(-)
prev parent reply other threads:[~2023-07-03 13:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 12:03 [PATCH v3] target/ppc: Make checkstop actually stop the system Nicholas Piggin
2023-07-03 12:26 ` BALATON Zoltan
2023-07-03 12:38 ` Daniel Henrique Barboza
2023-07-03 13:07 ` Nicholas Piggin
2023-07-03 15:06 ` BALATON Zoltan
2023-07-05 2:59 ` Nicholas Piggin
2023-07-06 11:33 ` BALATON Zoltan
2023-07-03 13:26 ` Philippe Mathieu-Daudé [this message]
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=9fbf9403-fbfe-4d84-7ca4-aae19e9d207e@linaro.org \
--to=philmd@linaro.org \
--cc=balaton@eik.bme.hu \
--cc=clg@kaod.org \
--cc=danielhb413@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--cc=harshpb@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=richard.henderson@linaro.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).