From: Matthew Rosato <mjrosato@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: agraf@suse.de, borntraeger@de.ibm.com,
bharata@linux.vnet.ibm.com, cornelia.huck@de.ibm.com,
pbonzini@redhat.com, afaerber@suse.de, rth@twiddle.net
Subject: [Qemu-devel] [PATCH v3 01/10] exec: Remove cpu from cpus list during cpu_exec_exit()
Date: Wed, 27 Jan 2016 11:53:32 -0500 [thread overview]
Message-ID: <1453913621-20961-2-git-send-email-mjrosato@linux.vnet.ibm.com> (raw)
In-Reply-To: <1453913621-20961-1-git-send-email-mjrosato@linux.vnet.ibm.com>
From: Bharata B Rao <bharata@linux.vnet.ibm.com>
CPUState *cpu gets added to the cpus list during cpu_exec_init(). It
should be removed from cpu_exec_exit().
cpu_exec_init() is called from generic CPU::instance_finalize and some
archs like PowerPC call it from CPU unrealizefn. So ensure that we
dequeue the cpu only once.
Now -1 value for cpu->cpu_index indicates that we have already dequeued
the cpu for CONFIG_USER_ONLY case also.
Signed-off-by: Bharata B Rao <bharata@linux.vnet.ibm.com>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
---
exec.c | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/exec.c b/exec.c
index 7115403..c8da9d4 100644
--- a/exec.c
+++ b/exec.c
@@ -596,6 +596,7 @@ void cpu_exec_exit(CPUState *cpu)
return;
}
+ QTAILQ_REMOVE(&cpus, cpu, node);
bitmap_clear(cpu_index_map, cpu->cpu_index, 1);
cpu->cpu_index = -1;
}
@@ -614,6 +615,15 @@ static int cpu_get_free_index(Error **errp)
void cpu_exec_exit(CPUState *cpu)
{
+ cpu_list_lock();
+ if (cpu->cpu_index == -1) {
+ cpu_list_unlock();
+ return;
+ }
+
+ QTAILQ_REMOVE(&cpus, cpu, node);
+ cpu->cpu_index = -1;
+ cpu_list_unlock();
}
#endif
--
1.9.1
next prev parent reply other threads:[~2016-01-27 16:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 16:53 [Qemu-devel] [PATCH v3 00/10] Allow hotplug of s390 CPUs Matthew Rosato
2016-01-27 16:53 ` Matthew Rosato [this message]
2016-01-27 16:53 ` [Qemu-devel] [PATCH v3 02/10] exec: Do vmstate unregistration from cpu_exec_exit() Matthew Rosato
2016-01-27 16:53 ` [Qemu-devel] [PATCH v3 03/10] cpu: Reclaim vCPU objects Matthew Rosato
2016-01-27 16:53 ` [Qemu-devel] [PATCH v3 04/10] cpu: Add a sync version of cpu_remove() Matthew Rosato
2016-01-27 16:53 ` [Qemu-devel] [PATCH v3 05/10] s390x/cpu: Cleanup init in preparation for hotplug Matthew Rosato
2016-01-27 16:53 ` [Qemu-devel] [PATCH v3 06/10] s390x/cpu: Set initial CPU state in common routine Matthew Rosato
2016-01-27 16:53 ` [Qemu-devel] [PATCH v3 07/10] s390x/cpu: Move some CPU initialization into realize Matthew Rosato
2016-01-30 12:01 ` David Hildenbrand
2016-01-27 16:53 ` [Qemu-devel] [PATCH v3 08/10] s390x/cpu: Add functions to (un)register CPU state Matthew Rosato
2016-01-27 16:53 ` [Qemu-devel] [PATCH v3 09/10] s390/virtio-ccw: Add hotplug handler and prepare for unplug Matthew Rosato
2016-01-27 16:53 ` [Qemu-devel] [PATCH v3 10/10] s390x/cpu: Allow hot plug/unplug of CPUs Matthew Rosato
2016-02-01 8:52 ` [Qemu-devel] [PATCH v3 00/10] Allow hotplug of s390 CPUs Christian Borntraeger
2016-02-10 15:28 ` David Hildenbrand
2016-02-10 16:28 ` Andreas Färber
2016-02-11 8:36 ` 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=1453913621-20961-2-git-send-email-mjrosato@linux.vnet.ibm.com \
--to=mjrosato@linux.vnet.ibm.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=bharata@linux.vnet.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).