From: Christian Borntraeger <borntraeger@linux.ibm.com>
To: Cornelia Huck <cohuck@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Pedro Barbuda <pbarbuda@microsoft.com>,
Mohamed Mediouni <mohamed@unpredictable.fr>,
Nicholas Piggin <npiggin@gmail.com>,
Harsh Prateek Bora <harshpb@linux.ibm.com>,
Eric Farman <farman@linux.ibm.com>,
Matthew Rosato <mjrosato@linux.ibm.com>,
"Daniel P. Berrange" <berrange@redhat.com>
Subject: Re: what is qemu_system_guest_panicked() for?
Date: Mon, 13 Jul 2026 15:53:09 +0200 [thread overview]
Message-ID: <1e02ef6d-2f36-4219-9c1d-680fd6426a67@linux.ibm.com> (raw)
In-Reply-To: <87ik6ji3zl.fsf@redhat.com>
Am 13.07.26 um 12:22 schrieb Cornelia Huck:
>> Cases which are not:
[...]
>> - s390_handle_wait(): not sure exactly what this is
>
> Loading a "disabled wait PSW" (waiting for interrupts with no interrupts
> enabled) is basically the way for an OS to "panic". (The "special wait
> PSW" is for signifying that a cpu has been shut down.) IOW, this is
> indeed the "panic" case for s390x.
[...]
>> - s390 unmanageable_intercept(): again not sure, think this is where
>> the guest has gone off the rails and we can't keep running
>
> It's basically "the handling code for an exception immediately leads to
> the same exception", the cpu has gone into a loop and can't get out of
> it again. Not sure if that should be getting some different handling.
Right. I think having both cases in the same bucket makes sense.
next prev parent reply other threads:[~2026-07-13 13:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 16:02 what is qemu_system_guest_panicked() for? Peter Maydell
2026-07-11 15:01 ` Harsh Prateek Bora
2026-07-13 8:39 ` Daniel P. Berrangé
2026-07-13 8:57 ` Markus Armbruster
2026-07-13 9:06 ` Daniel P. Berrangé
2026-07-13 10:30 ` Cornelia Huck
2026-07-13 11:43 ` Markus Armbruster
2026-07-13 12:14 ` Daniel P. Berrangé
2026-07-13 13:57 ` Markus Armbruster
2026-07-13 15:02 ` Daniel P. Berrangé
2026-07-13 18:09 ` Markus Armbruster
2026-07-13 12:30 ` Peter Maydell
2026-07-13 10:22 ` Cornelia Huck
2026-07-13 13:53 ` Christian Borntraeger [this message]
2026-07-13 13:36 ` Fabiano Rosas
2026-07-14 10:24 ` Aditya Gupta
2026-07-14 14:47 ` Shivang Upadhyay
2026-07-14 17:19 ` Fabiano Rosas
2026-07-13 14:49 ` Fabiano Rosas
2026-07-13 15:03 ` Peter Maydell
2026-07-13 16:11 ` Fabiano Rosas
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=1e02ef6d-2f36-4219-9c1d-680fd6426a67@linux.ibm.com \
--to=borntraeger@linux.ibm.com \
--cc=berrange@redhat.com \
--cc=cohuck@redhat.com \
--cc=farman@linux.ibm.com \
--cc=harshpb@linux.ibm.com \
--cc=mjrosato@linux.ibm.com \
--cc=mohamed@unpredictable.fr \
--cc=npiggin@gmail.com \
--cc=pbarbuda@microsoft.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.