From: David Hildenbrand <david@redhat.com>
To: qemu-s390x@nongnu.org
Cc: qemu-devel@nongnu.org, Richard Henderson <rth@twiddle.net>,
Alexander Graf <agraf@suse.de>, Cornelia Huck <cohuck@redhat.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Thomas Huth <thuth@redhat.com>,
David Hildenbrand <david@redhat.com>
Subject: [Qemu-devel] [PATCH v2 7/7] s390x/tcg: fix CPU hotplug with single-threaded TCG
Date: Wed, 20 Jun 2018 12:08:25 +0200 [thread overview]
Message-ID: <20180620100825.22476-8-david@redhat.com> (raw)
In-Reply-To: <20180620100825.22476-1-david@redhat.com>
run_on_cpu() doesn't seem to work reliably until the CPU has been fully
created if the single-threaded TCG main loop is already running.
Therefore, let's use run_on_cpu() for KVM only - KVM requires it due to
the initial CPU reset ioctl.
Signed-off-by: David Hildenbrand <david@redhat.com>
---
target/s390x/cpu.c | 11 ++++++-----
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/target/s390x/cpu.c b/target/s390x/cpu.c
index 40d6980229..7536dd0f03 100644
--- a/target/s390x/cpu.c
+++ b/target/s390x/cpu.c
@@ -218,11 +218,12 @@ static void s390_cpu_realizefn(DeviceState *dev, Error **errp)
#endif
s390_cpu_gdb_init(cs);
qemu_init_vcpu(cs);
-#if !defined(CONFIG_USER_ONLY)
- run_on_cpu(cs, s390_do_cpu_full_reset, RUN_ON_CPU_NULL);
-#else
- cpu_reset(cs);
-#endif
+
+ if (kvm_enabled()) {
+ run_on_cpu(cs, s390_do_cpu_full_reset, RUN_ON_CPU_NULL);
+ } else {
+ cpu_reset(cs);
+ }
scc->parent_realize(dev, &err);
out:
--
2.17.1
next prev parent reply other threads:[~2018-06-20 10:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 10:08 [Qemu-devel] [PATCH v2 0/7] s390x: TOD refactoring + TCG CPU hotplug support David Hildenbrand
2018-06-20 10:08 ` [Qemu-devel] [PATCH v2 1/7] s390x/tod: factor out TOD into separate device David Hildenbrand
2018-06-21 11:15 ` Thomas Huth
2018-06-21 11:51 ` David Hildenbrand
2018-06-20 10:08 ` [Qemu-devel] [PATCH v2 2/7] s390x/tcg: drop tod_basetime David Hildenbrand
2018-06-21 11:33 ` Thomas Huth
2018-06-20 10:08 ` [Qemu-devel] [PATCH v2 3/7] s390x/tcg: properly implement the TOD David Hildenbrand
2018-06-20 19:33 ` Richard Henderson
2018-06-20 20:33 ` David Hildenbrand
2018-06-20 21:00 ` Richard Henderson
2018-06-21 11:44 ` Thomas Huth
2018-06-21 11:52 ` David Hildenbrand
2018-06-20 10:08 ` [Qemu-devel] [PATCH v2 4/7] s390x/tcg: SET CLOCK COMPARATOR can clear CKC interrupts David Hildenbrand
2018-06-21 12:09 ` Thomas Huth
2018-06-21 13:54 ` David Hildenbrand
2018-06-21 14:01 ` [Qemu-devel] [qemu-s390x] " Thomas Huth
2018-06-21 14:10 ` [Qemu-devel] " Cornelia Huck
2018-06-21 13:58 ` Cornelia Huck
2018-06-21 14:03 ` David Hildenbrand
2018-06-20 10:08 ` [Qemu-devel] [PATCH v2 5/7] s390x/tcg: implement SET CLOCK David Hildenbrand
2018-06-21 13:14 ` Thomas Huth
2018-06-21 14:01 ` David Hildenbrand
2018-06-21 14:23 ` Cornelia Huck
2018-06-20 10:08 ` [Qemu-devel] [PATCH v2 6/7] s390x/tcg: rearm the CKC timer during migration David Hildenbrand
2018-06-21 13:18 ` Thomas Huth
2018-06-20 10:08 ` David Hildenbrand [this message]
2018-06-21 13:22 ` [Qemu-devel] [PATCH v2 7/7] s390x/tcg: fix CPU hotplug with single-threaded TCG Thomas Huth
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=20180620100825.22476-8-david@redhat.com \
--to=david@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@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 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).