From: Paolo Bonzini <pbonzini@redhat.com>
To: David Hildenbrand <david@redhat.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Cornelia Huck <cohuck@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
qemu-s390x <qemu-s390x@nongnu.org>,
Thomas Huth <thuth@redhat.com>,
Halil Pasic <pasic@linux.vnet.ibm.com>,
Janosch Frank <frankja@linux.vnet.ibm.com>,
Alexander Graf <agraf@suse.de>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH 1/1] s390/ipl: fix ipl with -no-reboot
Date: Thu, 21 Jun 2018 19:06:59 +0200 [thread overview]
Message-ID: <159d794c-58b3-ceba-e286-2e585d9a661a@redhat.com> (raw)
In-Reply-To: <57057de1-b1dd-bc22-eb98-1325c499f591@redhat.com>
On 21/06/2018 18:31, David Hildenbrand wrote:
> + SHUTDOWN_CAUSE_GUEST_RESET_FORCE,/* Guest reset that should ignore
> + --no-reboot. This is useful for reset
> + like actions as s390 kexec/kdump */
> SHUTDOWN_CAUSE__MAX,
> } ShutdownCause;
>
> diff --git a/vl.c b/vl.c
> index b3426e03d0..722c3b9963 100644
> --- a/vl.c
> +++ b/vl.c
> @@ -1674,7 +1674,7 @@ void qemu_system_guest_panicked(GuestPanicInformation *info)
>
> void qemu_system_reset_request(ShutdownCause reason)
> {
> - if (no_reboot) {
> + if (no_reboot && reason != SHUTDOWN_CAUSE_GUEST_RESET_FORCE) {
> shutdown_requested = reason;
> } else {
> reset_requested = reason;
The only comment is that I'd drop the event too. It's not possible to
use SHUTDOWN_CAUSE_NONE directly of course, but you can special case it
in qemu_system_reset.
Also I wouldn't be worried of picking an s390-specific name like
SHUTDOWN_CAUSE_GUEST_(RE)?IPL. At least it explains exactly what it is
for and it makes sense that it doesn't obey -no-reboot and generate the
event.
Paolo
prev parent reply other threads:[~2018-06-21 17:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 16:25 [Qemu-devel] [PATCH 1/1] s390/ipl: fix ipl with -no-reboot Christian Borntraeger
2018-06-21 16:31 ` David Hildenbrand
2018-06-21 17:06 ` Paolo Bonzini [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=159d794c-58b3-ceba-e286-2e585d9a661a@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.vnet.ibm.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
--cc=thuth@redhat.com \
/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).