From: Paolo Bonzini <pbonzini@redhat.com>
To: 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>,
David Hildenbrand <david@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 v4] s390/ipl: fix ipl with -no-reboot
Date: Fri, 22 Jun 2018 14:12:55 +0200 [thread overview]
Message-ID: <bb7c5829-bf46-a1d0-7191-28b3202ddc98@redhat.com> (raw)
In-Reply-To: <20180622102928.173420-1-borntraeger@de.ibm.com>
On 22/06/2018 12:29, Christian Borntraeger wrote:
> kexec/kdump as well as the bootloader use a subcode of diagnose 308
> that is supposed to reset the I/O subsystem but not comprise a full
> "reboot". With the latest refactoring this is now broken when
> -no-reboot is used or when libvirt acts on a reboot QMP event, for
> example a virt-install from iso images.
> We need to mark these "subsystem reset" as special.
>
> Fixes: a30fb811cbe9 (s390x: refactor reset/reipl handling)
> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
> Reviewed-by: David Hildenbrand <david@redhat.com>
> ---
> v3->v4: - rename to SHUTDOWN_CAUSE_SUBSYSTEM_RESET
> - modify comments and patch descriptions
>
> hw/s390x/ipl.c | 8 +++++++-
> include/sysemu/sysemu.h | 4 ++++
> vl.c | 4 ++--
> 3 files changed, 13 insertions(+), 3 deletions(-)
>
> diff --git a/hw/s390x/ipl.c b/hw/s390x/ipl.c
> index 0d67349004..f278036fa7 100644
> --- a/hw/s390x/ipl.c
> +++ b/hw/s390x/ipl.c
> @@ -535,7 +535,13 @@ void s390_ipl_reset_request(CPUState *cs, enum s390_reset reset_type)
> ipl->iplb_valid = s390_gen_initial_iplb(ipl);
> }
> }
> - qemu_system_reset_request(SHUTDOWN_CAUSE_GUEST_RESET);
> + if (reset_type == S390_RESET_MODIFIED_CLEAR ||
> + reset_type == S390_RESET_LOAD_NORMAL) {
> + /* ignore -no-reboot, send no event */
> + qemu_system_reset_request(SHUTDOWN_CAUSE_SUBSYSTEM_RESET);
> + } else {
> + qemu_system_reset_request(SHUTDOWN_CAUSE_GUEST_RESET);
> + }
> /* as this is triggered by a CPU, make sure to exit the loop */
> if (tcg_enabled()) {
> cpu_loop_exit(cs);
> diff --git a/include/sysemu/sysemu.h b/include/sysemu/sysemu.h
> index e893f72f3b..9a621de02f 100644
> --- a/include/sysemu/sysemu.h
> +++ b/include/sysemu/sysemu.h
> @@ -44,6 +44,10 @@ typedef enum ShutdownCause {
> turns that into a shutdown */
> SHUTDOWN_CAUSE_GUEST_PANIC, /* Guest panicked, and command line turns
> that into a shutdown */
> + SHUTDOWN_CAUSE_SUBSYSTEM_RESET,/* Partial guest reset that does not trigger
> + QMP events and ignores --no-reboot. This
> + is useful for sanitize hypercalls on s390
> + that are used during kexec/kdump/boot */
> SHUTDOWN_CAUSE__MAX,
> } ShutdownCause;
>
> diff --git a/vl.c b/vl.c
> index b3426e03d0..c196e39287 100644
> --- a/vl.c
> +++ b/vl.c
> @@ -1628,7 +1628,7 @@ void qemu_system_reset(ShutdownCause reason)
> } else {
> qemu_devices_reset();
> }
> - if (reason) {
> + if (reason != SHUTDOWN_CAUSE_SUBSYSTEM_RESET) {
> qapi_event_send_reset(shutdown_caused_by_guest(reason),
> &error_abort);
> }
> @@ -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_SUBSYSTEM_RESET) {
> shutdown_requested = reason;
> } else {
> reset_requested = reason;
>
Acked-by: Paolo Bonzini <pbonzini@redhat.com>
Thanks!
Paolo
next prev parent reply other threads:[~2018-06-22 12:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 10:29 [Qemu-devel] [PATCH v4] s390/ipl: fix ipl with -no-reboot Christian Borntraeger
2018-06-22 12:12 ` Paolo Bonzini [this message]
2018-06-22 12:14 ` Halil Pasic
2018-06-22 13:22 ` no-reply
2018-06-22 13:29 ` Christian Borntraeger
2018-06-22 13:47 ` Cornelia Huck
2018-06-22 14:10 ` Eric Blake
2018-06-22 13:50 ` Cornelia Huck
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=bb7c5829-bf46-a1d0-7191-28b3202ddc98@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).