From: Cornelia Huck <cohuck@redhat.com>
To: Janosch Frank <frankja@linux.ibm.com>
Cc: thuth@redhat.com, pmorel@linux.ibm.com, david@redhat.com,
qemu-devel@nongnu.org, borntraeger@de.ibm.com,
qemu-s390x@nongnu.org, mihajlov@linux.ibm.com
Subject: Re: [PATCH v2 1/5] s390x: Don't do a normal reset on the initial cpu
Date: Fri, 22 Nov 2019 17:17:33 +0100 [thread overview]
Message-ID: <20191122171733.3d60d767.cohuck@redhat.com> (raw)
In-Reply-To: <20191122140002.42972-2-frankja@linux.ibm.com>
On Fri, 22 Nov 2019 08:59:58 -0500
Janosch Frank <frankja@linux.ibm.com> wrote:
> The initiating cpu needs to be reset with an initial reset. While
> doing a normal reset followed by a initial reset is not wron per-se,
s/wron per-se/wrong per se/
> the Ultravisor will only allow the correct reset to be performed.
So... the uv has stricter rules than the architecture has in that
respect?
>
> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
> Reviewed-by: David Hildenbrand <david@redhat.com>
> ---
> hw/s390x/s390-virtio-ccw.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/hw/s390x/s390-virtio-ccw.c b/hw/s390x/s390-virtio-ccw.c
> index d3edeef0ad..c1d1440272 100644
> --- a/hw/s390x/s390-virtio-ccw.c
> +++ b/hw/s390x/s390-virtio-ccw.c
> @@ -348,6 +348,9 @@ static void s390_machine_reset(MachineState *machine)
> break;
> case S390_RESET_LOAD_NORMAL:
> CPU_FOREACH(t) {
> + if (t == cs) {
> + continue;
> + }
> run_on_cpu(t, s390_do_cpu_reset, RUN_ON_CPU_NULL);
> }
> subsystem_reset();
next prev parent reply other threads:[~2019-11-22 16:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 13:59 [PATCH v2 0/5] s390x: Reset cleanup Janosch Frank
2019-11-22 13:59 ` [PATCH v2 1/5] s390x: Don't do a normal reset on the initial cpu Janosch Frank
2019-11-22 16:17 ` Cornelia Huck [this message]
2019-11-22 16:55 ` Janosch Frank
2019-11-22 13:59 ` [PATCH v2 2/5] s390x: Move reset normal to shared reset handler Janosch Frank
2019-11-22 14:12 ` David Hildenbrand
2019-11-22 14:00 ` [PATCH v2 3/5] s390x: Move initial reset Janosch Frank
2019-11-22 14:21 ` David Hildenbrand
2019-11-22 14:00 ` [PATCH v2 4/5] s390x: Move clear reset Janosch Frank
2019-11-22 14:30 ` David Hildenbrand
2019-11-22 16:53 ` Janosch Frank
2019-11-22 17:15 ` Janosch Frank
2019-11-22 17:17 ` David Hildenbrand
2019-11-22 14:00 ` [PATCH v2 5/5] s390x: Beautify diag308 handling Janosch Frank
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=20191122171733.3d60d767.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=mihajlov@linux.ibm.com \
--cc=pmorel@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--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.