From: Cornelia Huck <cohuck@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
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 v3 1/1] s390/ipl: fix ipl with -no-reboot
Date: Fri, 22 Jun 2018 11:46:59 +0200 [thread overview]
Message-ID: <20180622114659.7858fe00.cohuck@redhat.com> (raw)
In-Reply-To: <c4ce8f0c-ccbb-3d79-459f-bb771a68685a@de.ibm.com>
On Thu, 21 Jun 2018 22:34:49 +0200
Christian Borntraeger <borntraeger@de.ibm.com> wrote:
> On 06/21/2018 07:08 PM, Paolo Bonzini wrote:
> > On 21/06/2018 19:01, Christian Borntraeger wrote:
> >> kexec/kdump as well as the bootloader use a subcode of diagnose 308
> >> that is supposed to reset the subsystem but not comprise a full
> >> "reboot". With the latest refactoring this is now broken when
> >> -no-reboot is used. This for example breaks virt-install from
> >> iso images.
> >>
> >> We need to mark these "soft" reboots as ok for rebooting.
> >>
> >> Fixes: a30fb811cbe9 (s390x: refactor reset/reipl handling)
> >> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
> >
> > Ok, then my suggestion made even more sense. :) No other objections
> > apart from the name of the constant.
> >
> > Paolo
>
> SHUTDOWN_CAUSE_S390_PARTIAL ?
Don't like that one much.
>
> SHUTDOWN_CAUSE_S390_SUBSYS_RESET?
Either that, or drop the 'S390' (is it conceivable that other
architectures have something similar)?
>
>
> >
> >> ---
> >> hw/s390x/ipl.c | 8 +++++++-
> >> include/sysemu/sysemu.h | 3 +++
> >> vl.c | 4 ++--
> >> 3 files changed, 12 insertions(+), 3 deletions(-)
> >>
> >> diff --git a/hw/s390x/ipl.c b/hw/s390x/ipl.c
> >> index 0d67349004..ade6896af6 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 */
> >> + qemu_system_reset_request(SHUTDOWN_CAUSE_GUEST_RESET_FORCE);
> >> + } 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..345369d924 100644
> >> --- a/include/sysemu/sysemu.h
> >> +++ b/include/sysemu/sysemu.h
> >> @@ -44,6 +44,9 @@ typedef enum ShutdownCause {
> >> turns that into a shutdown */
> >> SHUTDOWN_CAUSE_GUEST_PANIC, /* Guest panicked, and command line turns
> >> that into a shutdown */
> >> + 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..44e65071bc 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_GUEST_RESET_FORCE) {
> >> 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_GUEST_RESET_FORCE) {
> >> shutdown_requested = reason;
> >> } else {
> >> reset_requested = reason;
> >>
> >
>
The patch looks sane to me.
next prev parent reply other threads:[~2018-06-22 9:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 17:01 [Qemu-devel] [PATCH v3 1/1] s390/ipl: fix ipl with -no-reboot Christian Borntraeger
2018-06-21 17:08 ` Paolo Bonzini
2018-06-21 20:34 ` Christian Borntraeger
2018-06-22 9:46 ` Cornelia Huck [this message]
2018-06-22 9:59 ` Paolo Bonzini
2018-06-22 10:10 ` Christian Borntraeger
2018-06-22 10:10 ` David Hildenbrand
2018-06-22 7:01 ` David Hildenbrand
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=20180622114659.7858fe00.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.vnet.ibm.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=pbonzini@redhat.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 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.